Dlink DIR-825 B1 status [updated] [status 3 - MAC addrs PATCH]

Tue Sep 3 20:20:50 UTC 2013

On Fri, August 23, 2013 04:20, Adrian Chadd wrote:
> hah! cute.
>
> Yeah, for now let's just commit this. We can tidy it up in a later pass.

Adrian,

is this already commited ?

I don't get the ath[0,1] in here.

is there any way to have sshd in it ?

att,

matheus

# dmesg
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-CURRENT #0 r254983: Wed Aug 28 15:44:20 BRT 2013
    root at dev:/root/work/freebsd/head/obj/mipseb/mips.mips/root/work/freebsd/head/src/sys/DIR-825 mips
gcc version 4.2.1 20070831 patched [FreeBSD]
WARNING: WITNESS option enabled, expect reduced performance.
MEMGUARD DEBUGGING ALLOCATOR INITIALIZED:
        MEMGUARD map base: 0xc0800000
        MEMGUARD map size: 104860 KBytes
real memory  = 67108864 (65536K bytes)
avail memory = 59285504 (56MB)
nexus0: <MIPS32 root nexus>
clock0: <Generic MIPS32 ticker> on nexus0
Timecounter "MIPS32" frequency 340000000 Hz quality 800
Event timer "MIPS32" frequency 340000000 Hz quality 800
apb0 at irq 4 on nexus0
uart0: <16550 or compatible> on apb0
uart0: console (115200,n,8,1)
pcib0 at irq 0 on nexus0
pcib0: ar71xx_pci_attach: missing hint 'baseslot', default to AR71XX_PCI_BASE_SLOT
pcib0: found EEPROM at 0x1f661000 on 0.17.0
pcib0: EEPROM firmware: 0x1f661000 @ 4096 bytes
pcib0: device EEPROM 'pcib.0.bus.0.17.0.eeprom_firmware' registered
pcib0: found EEPROM at 0x1f665000 on 0.18.0
pcib0: EEPROM firmware: 0x1f665000 @ 4096 bytes
pcib0: device EEPROM 'pcib.0.bus.0.18.0.eeprom_firmware' registered
pci0: <PCI bus> on pcib0
pci0: <network> at device 17.0 (no driver attached)
pci0: <network> at device 18.0 (no driver attached)
arge0: <Atheros AR71xx built-in ethernet interface> at mem 0x19000000-0x19000fff irq 2 on nexus0
arge0: Overriding MAC from EEPROM
arge0: Vendor stores MAC in ASCII format
arge0: finishing attachment, phymask 0000, proxy null
arge0: Ethernet address: xx
arge1: <Atheros AR71xx built-in ethernet interface> at mem 0x1a000000-0x1a000fff irq 3 on nexus0
arge1: Overriding MAC from EEPROM
arge1: Vendor stores MAC in ASCII format
arge1: finishing attachment, phymask 0000, proxy null
arge1: Ethernet address: xx
spi0: <AR71XX SPI> at mem 0x1f000000-0x1f00000f on nexus0
spibus0: <spibus bus> on spi0
mx25l0: <M25Pxx Flash Family> at cs 0 on spibus0
mx25l0: m25p64, sector 65536 bytes, 128 sectors
ar71xx_wdog0: <Atheros AR71XX watchdog timer> on nexus0
Timecounters tick every 1.000 msec
map/rootfs.uncompress: GEOM_ULZMA image found
map/rootfs.uncompress: 174 x 131072 blocks
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/map/rootfs.uncompress []...
warning: no time-of-day clock registered, system time will not be set accurately
random: <Software, Yarrow> initialized
bridge0: Ethernet address: xx

> -adrian
>
>
>
> On 22 August 2013 22:57, Sean Bruno <sean_bruno at yahoo.com> wrote:
>
>>
>> > Huh ... it looks like the caldata and the mac addrs are at "special"
>> > locations as the openwrt folks have special functions to read them in
>> > their "mach-dir-825-b1.c"
>> >
>> > I suspect that with this as a road map I can "do something" to try and
>> > pull in their specific methods to do stuff tonight.  Is this the right
>> > path to go down?
>> >
>> > Sean
>> >
>>
>> This amused me a bit today.  Turns out that the MAC addrs are stored as
>> a literal string for arge(4) on this board.  Took me a bit, but this
>> patch and change to DIR-825.hints gets "real" MAC addrs setup for arge0
>> and arge1.  I snickered a bit when I realized that they even left the
>> ":" characters in the string.
>>
>> I also add the "magic" numbers for reading the mac's from the EEPROM and
>> expose a "readascii" generalized hint for this supported class of
>> boards.
>>
>> Looking over openwrt's solution, they don't get MAC addresses for the
>> WLAN interfaces, then use the one's provided by arge(4) and simply add
>> 1.  I haven't reviewed the relevant ath(4) code to see how we can pass
>> that in, so suggestions are welcome.
>>
>> http://people.freebsd.org/~sbruno/arge_ascii.txt
>>
>> Sean
>>
>> p.s. dmesg updated
>> http://people.freebsd.org/~sbruno/dir_825_dmesg.txt
>>
> _______________________________________________
> freebsd-embedded at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded
> To unsubscribe, send any mail to "freebsd-embedded-unsubscribe at freebsd.org"
>

-- 
We will call you Cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style