ts-7000
[Top] [All Lists]

[ts-7000] Re: TS-7400 wireless driver question with kernel 2.6.29

To:
Subject: [ts-7000] Re: TS-7400 wireless driver question with kernel 2.6.29
From: "Derek" <>
Date: Thu, 04 Feb 2010 04:11:39 -0000

Looks like the 2.6.29 kernel driver is available in the modules tarball on the 
FTP site:
ftp://ftp.embeddedarm.com/application-kits/ts-wifibox/binaries/ts-modules/tskernelmodules-2.6.29-ts.tar.gz

Path: ./2.6.29-ts/kernel/drivers/net/wireless/zd1211rw/zd1211rw.ko

I haven't tested it myself so it would be interesting to know if it works.

Normal steps:
insmod zd1211rw.ko
cat /proc/net/wireless
ifconfig wlan0 up
iwlist scan
iwconfig wlan0 essid the_essid
etc..etc..etc..

Refer to the TS-WIFIBOX manual for the exact steps.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Derek Hildreth
Embedded Systems Engineer
Technologic Systems
-=-=-=-=-=-=-=-=-=-=-=-=-=-=


--- In  "mattfishburn" <> wrote:
>
> A bit more digging and I have discovered that my device actually uses the 
> zd1211rw driver, not the zd1201 driver.  The output from lsusb is:
>
> ts7000:/lib# lsusb
> Bus 001 Device 005: ID 0ace:1215 ZyDAS WLA-54L 802.11bg
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> ts7000:/lib#
>
> with device 0ace:1215 being listed under the zd1211rw driver:
>
> http://wiki.debian.org/zd1211rw
>
> The 2.6.29 kernel from TS does not appear to provide this module.  Did I miss 
> the module in the 2.6.29 kernel, or are there any provided 2.6 kernels that 
> include this module?  Or will I need to figure out how to compile this module 
> for the 2.6.29 kernel provided by TS, or compile my own kernel?
>
> Cheers,
> Matt
>
> --- In  "mattfishburn" <mattfishburn@> wrote:
> >
> > Hi,
> >
> > I'm running my TS-7400 with modifications to the hwclock scripts as 
> > described in this thread:
> >
> > http://tech.groups.yahoo.com/group/ts-7000/message/17097
> >
> > I am attempting to use my IOGear GWU523 with the device, however the zd1201 
> > driver doesn't seem to claim the device.  I've checked that the driver is 
> > listed in lsmod output, and the device clearly shows up in the dmesg 
> > output.  Am I missing a step to link the driver to claiming the USB device? 
> >  Here is my dmesg output (I plugged the USB WIFI adapter in after the board 
> > had booted).
> >
> > ts7000:~# dmesg
> > Linux version 2.6.29-ts  (gcc version 3.4.4 (release) (CodeSourcery 
> > ARM 2005q3-2)) #4 PREEMPT Sun May 17 15:02:44 MST 2009
> > CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
> > CPU: VIVT data cache, VIVT instruction cache
> > Machine: Technologic Systems TS-72xx SBC
> > Memory policy: ECC disabled, Data cache writeback
> > On node 0 totalpages: 16384
> >   Normal zone: 7344 pages used for memmap
> >   Normal zone: 0 pages reserved
> >   Normal zone: 9040 pages, LIFO batch:1
> > Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 9040
> > Kernel command line: root=/dev/ram0 rw init=/linuxrc lpj=498688 console=null
> > PID hash table entries: 256 (order: 8, 1024 bytes)
> > Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> > Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> > Memory: 8MB 8MB 8MB 8MB 8MB 8MB 8MB 8MB = 64MB total
> > Memory: 57412KB available (2912K code, 210K data, 116K init)
> > Calibrating delay loop (skipped) preset value.. 99.73 BogoMIPS (lpj=498688)
> > Mount-cache hash table entries: 512
> > CPU: Testing write buffer coherency: ok
> > net_namespace: 760 bytes
> > NET: Registered protocol family 16
> > ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz
> > ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz
> > bio: create slab <bio-0> at 0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP established hash table entries: 2048 (order: 2, 16384 bytes)
> > TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
> > TCP: Hash tables configured (established 2048 bind 2048)
> > TCP reno registered
> > NET: Registered protocol family 1
> > checking if image is initramfs...it isn't (bad gzip magic numbers); looks 
> > like an initrd
> > Freeing initrd memory: 4096K
> > NetWinder Floating Point Emulator V0.97 (extended precision)
> > JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
> > JFS: nTxBlock = 480, nTxLock = 3845
> > msgmni has been set to 120
> > alg: No test for stdrng (krng)
> > io scheduler noop registered
> > io scheduler deadline registered (default)
> > Serial: AMBA driver
> > apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
> > apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
> > apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
> > brd: module loaded
> > ep93xx-eth version 0.11 loading
> > eth0 (): not using net_device_ops yet
> > ep93xx_mii_bus: probed
> > Generic PHY 0:01: PHY supports MII frame preamble suppression
> > net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
> > net eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:41:00:7d
> > rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc0
> > rtc-m48t86 rtc-m48t86: battery ok
> > ep93xx_wdt: EP93XX watchdog, driver version 0.3
> > ts72xx_wdt: cannot register miscdev on minor=130 (err=-16)
> > ts72xx-wdt: probe of ts72xx-wdt failed with error -16
> > TCP cubic registered
> > NET: Registered protocol family 10
> > NET: Registered protocol family 17
> > NET: Registered protocol family 15
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > rtc-m48t86 rtc-m48t86: hctosys: invalid date/time
> > RAMDISK: ext2 filesystem found at block 0
> > RAMDISK: Loading 1536KiB [1 disk] into ram disk... done.
> > EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
> > VFS: Mounted root (ext2 filesystem) on device 1:0.
> > Freeing init memory: 116K
> > Warning: unable to open an initial console.
> > Searching for NAND flash...
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 
> > 8-bit)
> > Bad block table found at page 65504, version 0x01
> > Bad block table found at page 65472, version 0x01
> > Hardware ECC NOT detected!
> > Using MBR partition definition
> > Creating 4 MTD partitions on "NAND 32MiB 3,3V 8-bit":
> > 0x000000000000-0x000002000000 : "whole chip"
> > 0x000000004000-0x000000204000 : "kernel"
> > 0x000000204000-0x000000404000 : "initrd"
> > 0x000000404000-0x000002000000 : "rootfs"
> > tssdcard: Technologic Systems SD card controller, address 0xe8000100
> > size=0xf1f00
> > size=0xf1f00
> > tssdcard: card /dev/tssdcarda has 990976 sectors (LUN 0)
> >  tssdcarda: tssdcarda1 tssdcarda2 tssdcarda3 tssdcarda4
> > ttts0 at MMIO 0x12400000 (irq = 33) is a TSUART
> > PHY: 0:01 - Link is Up - 100/Full
> > eth0: no IPv6 routers present
> > Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> > usbcore: registered new interface driver usbfs
> > usbcore: registered new interface driver hub
> > usbcore: registered new device driver usb
> > ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> > ohci_hcd: block sizes: ed 64 td 64
> > ep93xx-ohci ep93xx-ohci: EP93xx OHCI
> > drivers/usb/core/inode.c: creating file 'devices'
> > drivers/usb/core/inode.c: creating file '001'
> > ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus number 1
> > ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000
> > ep93xx-ohci ep93xx-ohci: created debug files
> > ep93xx-ohci ep93xx-ohci: OHCI controller state
> > ep93xx-ohci ep93xx-ohci: OHCI 1.0, NO legacy support registers
> > ep93xx-ohci ep93xx-ohci: control 0x083 HCFS=operational CBSR=3
> > ep93xx-ohci ep93xx-ohci: cmdstatus 0x00000 SOC=0
> > ep93xx-ohci ep93xx-ohci: intrstatus 0x00000004 SF
> > ep93xx-ohci ep93xx-ohci: intrenable 0x8000005a MIE RHSC UE RD WDH
> > ep93xx-ohci ep93xx-ohci: hcca frame #0005
> > ep93xx-ohci ep93xx-ohci: roothub.a 02001203 POTPGT=2 NOCP NPS NDP=3(3)
> > ep93xx-ohci ep93xx-ohci: roothub.b 00000000 PPCM=0000 DR=0000
> > ep93xx-ohci ep93xx-ohci: roothub.status 00008000 DRWE
> > ep93xx-ohci ep93xx-ohci: roothub.portstatus [0] 0x00000100 PPS
> > ep93xx-ohci ep93xx-ohci: roothub.portstatus [1] 0x00000100 PPS
> > ep93xx-ohci ep93xx-ohci: roothub.portstatus [2] 0x00000100 PPS
> > usb usb1: default language 0x0409
> > usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > usb usb1: Product: EP93xx OHCI
> > usb usb1: Manufacturer: Linux 2.6.29-ts ohci_hcd
> > usb usb1: SerialNumber: ep93xx
> > usb usb1: uevent
> > usb usb1: usb_probe_device
> > usb usb1: configuration #1 chosen from 1 choice
> > usb usb1: adding 1-0:1.0 (config #1, interface 0)
> > usb 1-0:1.0: uevent
> > hub 1-0:1.0: usb_probe_interface
> > hub 1-0:1.0: usb_probe_interface - got id
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 3 ports detected
> > hub 1-0:1.0: standalone hub
> > hub 1-0:1.0: no power switching (usb 1.0)
> > hub 1-0:1.0: no over-current protection
> > hub 1-0:1.0: power on to power good time: 4ms
> > hub 1-0:1.0: local power source is good
> > hub 1-0:1.0: trying to enable port power on non-switchable hub
> > drivers/usb/core/inode.c: creating file '001'
> > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> > SCSI subsystem initialized
> > Driver 'sd' needs updating - please use bus_type methods
> > Initializing USB Mass Storage driver...
> > usbcore: registered new interface driver usb-storage
> > USB Mass Storage support registered.
> > usbcore: registered new interface driver usbhid
> > usbhid: v2.6:USB HID core driver
> > usbcore: registered new interface driver zd1201
> > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0008
> > ep93xx-ohci ep93xx-ohci: GetStatus roothub.portstatus [2] = 0x00010101 CSC 
> > PPS CCS
> > hub 1-0:1.0: port 3, status 0101, change 0001, 12 Mb/s
> > hub 1-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x101
> > ep93xx-ohci ep93xx-ohci: GetStatus roothub.portstatus [2] = 0x00100103 PRSC 
> > PPS PES CCS
> > usb 1-3: new full speed USB device using ep93xx-ohci and address 2
> > ep93xx-ohci ep93xx-ohci: GetStatus roothub.portstatus [2] = 0x00100103 PRSC 
> > PPS PES CCS
> > usb 1-3: default language 0x0409
> > usb 1-3: New USB device found, idVendor=0ace, idProduct=1215
> > usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=0
> > usb 1-3: Product: USB2.0 WLAN
> > usb 1-3: Manufacturer: ZyDAS
> > usb 1-3: uevent
> > usb 1-3: usb_probe_device
> > usb 1-3: configuration #1 chosen from 1 choice
> > usb 1-3: adding 1-3:1.0 (config #1, interface 0)
> > usb 1-3:1.0: uevent
> > drivers/usb/core/inode.c: creating file '002'
> > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0008
> > ts7000:~# uname -a
> > Linux ts7000 2.6.29-ts #4 PREEMPT Sun May 17 15:02:44 MST 2009 armv4tl 
> > GNU/Linux
> > ts7000:~#
> >
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
    
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU