Re: [OpenWrt-Devel] Board identification and machine on /proc/cpuinfo for atheros platform

2011-11-16 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hanno, the interesting bits are in package/madwifi/patches/384-hwdetect.patch . Basically the model name is inferred from the PCI IDs of the radio, this might work for some popular appliances but I guess it will fail for generic boards with

Re: [OpenWrt-Devel] Board identification and machine on /proc/cpuinfo for atheros platform

2011-11-16 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is this information of 'vendor id' and 'subsys id' visible somewhere in 'user land' i.e on the command line, possibly with additional packages like pciutils? or some other way? Yep, see /sys/bus/pci/devices/*/vendor and

[OpenWrt-Devel] Board identification and machine on /proc/cpuinfo for atheros platform

2011-10-26 Thread Hanno Schupp
Dear all, I have recently switched from backfire to trunk. This forced a change from madwifi to ath5k for atheros platforms. I also compile and test firmware on ar71xx, ramips and brcm47xx. I notice that on ar71xx and ramips the actual router/board is identified in /proc/cpuinfo. Luci in trunk