Update: I was able to (I think) sort out the kernel config by using make
menuconfig and with the help of search (/), find the parameters suggested,
change them, and re-build the image. Unfortunately it seems as though
these kernel config options aren't correct: it just hangs after "using base
address...".
Recovery Bootloader
(C) Copyright 1999-2006, Secure Computing Inc (www.securecomputing.com)
SecureComputing/SG560 Version 3.1.5u1
'n'etwork, 'f'lash, 's'erial [n] :
Timeout, initiating network
Decompressing etherboot
+Getting DHCP address... .
Ethernet eth0: MAC address 00:d0:cf:0b:b9:34
IP: 192.168.0.101/255.255.255.0, Gateway: 192.168.0.1
Default server: 192.168.0.254, DNS server IP: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [RAM]
Red Hat certified release, version 1.94 - built 16:02:10, Nov 4 2005
Platform: CyberGuard SG5XX family of VPN/Firewall/Routers (XScale) BE
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x01000000, 0x00060d48-0x00ff3000 available
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> load -v -s 0x00200000 -b 0x00800000 image.bin
Using default protocol (TFTP)
|
Raw file loaded 0x00200000-0x002c65f8, assumed entry at 0x00200000
RedBoot> exec -r 0x00800000 -c "console=ttyS0,115200 root=/dev/ram0"
0x00200000
[Using ramdisk at 0x800000-0xbcf000]
Using base address 0x00200000 and length 0x000c65fc
Power light and the port lights are solid.
On Sat, Aug 30, 2014 at 8:20 PM, GravyFace <gravyf...@gmail.com> wrote:
> Hi Greg,
>
> Searched online for where to place those kernel config entries; tried to
> add them to the symlink'ed config.arch in the root snapgear-4.0.7 directory
> but that made 'make' unhappy.
>
> Where should I be placing those config lines? There's oodles of files
> with similar "CONFIG_" lines, so not sure where I should be putting it.
>
> Thanks
>
>
> On Fri, Aug 29, 2014 at 2:28 AM, Greg Ungerer <g...@uclinux.org> wrote:
>
>>
>> Hi,
>>
>> On 29/08/14 00:09, GravyFace wrote:
>> > Sure, here you go:
>> >
>> > Recovery Bootloader
>> > (C) Copyright 1999-2006, Secure Computing Inc (www.securecomputing.com
>> <http://www.securecomputing.com>)
>> > SecureComputing/SG560 Version 3.1.5u1
>> > 'n'etwork, 'f'lash, 's'erial [n] :
>> > Recovery Bootloader
>> > (C) Copyright 1999-2006, Secure Computing Inc (www.securecomputing.com
>> <http://www.securecomputing.com>)
>> > SecureComputing/SG560 Version 3.1.5u1
>> > 'n'etwork, 'f'lash, 's'erial [n] :
>> > Timeout, initiating network
>> > Decompressing etherboot
>> > +Getting DHCP address... .
>> > Ethernet eth0: MAC address 00:d0:cf:0b:b9:34
>> > IP: 192.168.0.101/255.255.255.0 <http://192.168.0.101/255.255.255.0>,
>> Gateway: 192.168.0.1
>> > Default server: 192.168.0.254, DNS server IP: 0.0.0.0
>> >
>> > RedBoot(tm) bootstrap and debug environment [RAM]
>> > Red Hat certified release, version 1.94 - built 16:02:10, Nov 4 2005
>> >
>> > Platform: CyberGuard SG5XX family of VPN/Firewall/Routers (XScale) BE
>> > Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
>> >
>> > RAM: 0x00000000-0x01000000, 0x00060d48-0x00ff3000 available
>> > == Executing boot script in 1.000 seconds - enter ^C to abort
>> > RedBoot> load -v -s 0x00200000 -b 0x00800000 image.bin
>> > Using default protocol (TFTP)
>> > |
>> > Raw file loaded 0x00200000-0x002c4b8c, assumed entry at 0x00200000
>> > RedBoot> exec -r 0x00800000 -c "console=ttyS0,115200 root=/dev/ram0"
>> 0x00200000
>> > [Using ramdisk at 0x800000-0xbce000]
>> > Using base address 0x00200000 and length 0x000c4b90
>> > Linux version 2.6.26-uc0 (root@test-ubu01) (gcc version 3.4.4) #13 Tue
>> Aug 26 12:14:17 EDT 2014
>> > CPU: XScale-IXP42x Family [690541f2] revision 2 (ARMv5TE), cr=000039ff
>> > Machine: McAfee/SG560
>> > Memory policy: ECC disabled, Data cache writeback
>> > CPU0: D VIVT undefined 5 cache
>> > CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> > CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> > Built 1 zonelists in Zone order, mobility grouping off. Total pages:
>> 4064
>> > Kernel command line: console=ttyS0,115200 root=/dev/ram0
>> > PID hash table entries: 64 (order: 6, 256 bytes)
>> > Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
>> > Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
>> > Memory: 16MB = 16MB total
>> > Memory: 14616KB available (1428K code, 96K data, 60K init)
>> > SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
>> > Mount-cache hash table entries: 512
>> > CPU: Testing write buffer coherency: ok
>> > net_namespace: 484 bytes
>> > NET: Registered protocol family 16
>> > IXP4xx: Using 16MiB expansion bus window size
>> > NET: Registered protocol family 2
>> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>> > TCP established hash table entries: 512 (order: 0, 4096 bytes)
>> > TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>> > TCP: Hash tables configured (established 512 bind 1024)
>> > TCP reno registered
>> > NET: Registered protocol family 1
>> > NetWinder Floating Point Emulator V0.97 (double precision)
>> > Squashfs 2.2-r2 (released 2005/09/08) (C) 2002-2005 Phillip Lougher
>> > Squashfs 2.2 includes LZMA decompression support
>> > io scheduler noop registered (default)
>> > ledman: Copyright (C) SnapGear, 2000-2008.
>> > LED: registered ERASE switch on IRQ26
>> > M41T11M6: Real Time Clock driver
>> > snapdog: HW/SW watchdog timer for SnapGear/Others
>> > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
>> disabled
>> > serial8250.0: ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
>> > console [ttyS0] enabled
>> > serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
>> > PPP generic driver version 2.4.2
>> > PPP Deflate Compression module registered
>> > PPP BSD Compression module registered
>> > PPP MPPE Compression module registered
>> > NET: Registered protocol family 24
>> > SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
>> > CSLIP: code copyright 1989 Regents of the University of California.
>> > SnapGear: MTD flash setup
>> > SnapGear Intel/StrataFlash: Found 1 x16 devices at 0x0 in 16-bit bank
>> > Intel/Sharp Extended Query Table at 0x0031
>> > Using buffer write method
>> > cfi_cmdset_0001: Erase suspend on write enabled
>> > SnapGear: SnapGear Intel/StrataFlash device size = 8192K
>> > Creating 6 MTD partitions on "SnapGear Intel/StrataFlash":
>> > 0x00000000-0x00020000 : "SnapGear Boot Loader"
>> > 0x00020000-0x000a0000 : "SnapGear non-volatile configuration"
>> > 0x000a0000-0x007e0000 : "SnapGear image"
>> > 0x00000000-0x00800000 : "SnapGear Intel/StrataFlash"
>> > 0x007e0000-0x00800000 : "SnapGear System Log"
>> > 0x007e0000-0x00800000 : "SnapGear System Log"
>> > SNAPARM: root device set to 2
>> > u32 classifier
>> > GRE over IPv4 tunneling driver
>> > TCP cubic registered
>> > NET: Registered protocol family 17
>> > Bridge firewalling registered
>> > 802.1Q VLAN Support v1.8 Ben Greear <gree...@candelatech.com <mailto:
>> gree...@candelatech.com>>
>> > All bugs added by David S. Miller <da...@redhat.com <mailto:
>> da...@redhat.com>>
>> > XScale DSP coprocessor detected.
>> > VFS: Cannot open root device "ram0" or unknown-block(0,0)
>> > Please append a correct "root=" boot option; here are the available
>> partitions:
>> > 1f00 128 mtdblock0 (driver?)
>> > 1f01 512 mtdblock1 (driver?)
>> > 1f02 7424 mtdblock2 (driver?)
>> > 1f03 8192 mtdblock3 (driver?)
>> > 1f04 128 mtdblock4 (driver?)
>> > 1f05 128 mtdblock5 (driver?)
>> > Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>>
>> I suspect you need these enabled:
>>
>> CONFIG_BLK_DEV_INITRD=y
>> CONFIG_BLK_DEV_RAM=y
>> CONFIG_BLK_DEV_RAM_COUNT=4
>> CONFIG_BLK_DEV_RAM_SIZE=16384
>>
>> Doesn't look like they are on from the output above.
>> Otherwise it looks ok.
>>
>> Regards
>> Greg
>>
>>
>>
>> > On Wed, Aug 27, 2014 at 8:02 PM, Greg Ungerer <g...@uclinux.org
>> <mailto:g...@uclinux.org>> wrote:
>> >
>> > On 27/08/14 23:09, GravyFace wrote:
>> >
>> > On Tue, Aug 26, 2014 at 8:44 PM, Greg Ungerer <g...@uclinux.org
>> <mailto:g...@uclinux.org> <mailto:g...@uclinux.org <mailto:
>> g...@uclinux.org>>> wrote:
>> > I'm assuming this was the last step,
>> >
>> > That is the last step. Easiest fix is to just create a
>> /tftpboot
>> > directory that is world read/write. Doesn't really matter
>> whether
>> > you actually have tftp server enabled or not.
>> >
>> > Yeah, I was able to figure that out and with the help of the SG
>> manual (amazing, those!) found out about the "recovery" process of holding
>> down ERASE and booting. With Wireshark, I was able to see it pick up an IP
>> from tftpd's DHCP service and successfully download my image.bin.
>> >
>> >
>> > Maybe, maybe not. What are the front LEDs doing?
>> > If the heartbeat (HB) is flashing then it was probably
>> successful.
>> >
>> > A serial port console is not enabled by default, so you
>> won't get
>> > anything on the serial port without doing extra steps.
>> >
>> > Now that I have that out of my system, my next step is
>> to install tftpd and (I'm assuming) do a TFTP based install? Don't see
>> that part on the snapgear.org <http://snapgear.org> <http://snapgear.org>
>> <http://snapgear.org> documentation on archive.org <http://archive.org> <
>> http://archive.org> <http://archive.org>, but maybe I'm missing
>> something.
>> >
>> >
>> > SnapGear has been shutdown so I don't know they have on the
>> web anymore.
>> > But the tftp network load is pretty simple. To see what is
>> going on hook
>> > up the serial port at 115200,8,n,1. Then hold in the ERASE
>> button and
>> > plug in the power. It will come up with a simple boot
>> loader prompt.
>> > After a few seconds it will timeout and try a network load
>> - doing a
>> > dhcp address lookup and then trying a tftp load of a system
>> image
>> > (that is the image.bin file that your compile generated).
>> >
>> >
>> > Well, getting a kernel panic; don't think it can find the flash
>> device...
>> >
>> > XScale DSP coprocessor detected.
>> > VFS: Cannot open root device "ram0" or unknown-block(0,0)
>> > Please append a correct "root=" boot option; here are the
>> available partitions:
>> > 1f00 128 mtdblock0 (driver?)
>> > 1f01 512 mtdblock1 (driver?)
>> > 1f02 7424 mtdblock2 (driver?)
>> > 1f03 8192 mtdblock3 (driver?)
>> > 1f04 128 mtdblock4 (driver?)
>> > 1f05 128 mtdblock5 (driver?)
>> > Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>> >
>> >
>> > Can you send the complete boot log?
>> >
>> >
>> > There was a patch that I never applied as I wasn't sure what
>> the architecture was for these, but seeing this in the boot message ("CPU:
>> XScale-IXP42x Family [690541f2] revision 2 (ARMv5TE), cr=000039ff"), it
>> jogged my memory of this, from the archive.org <http://archive.org> <
>> http://archive.org>'s snapgear documentation page:
>> >
>> >
>> > "Also available is a patch package that can be used to build
>> the Intel IXP4xx Access Library code as part of the SnapGear distribution.
>> This patch set contains support for the Intel CSR-1.4 with DSR-2.6.2
>> combination, and the Intel CSR-2.4 library (on both 2.4 and 2.6 linux
>> kernels)."
>> >
>> > There's also this, but it appears as those RedBoot has already
>> been configured:
>> >
>> https://gitorious.org/linux-__nios2/uclinux-dist/source/__5316285bb1b0a07bd2a2a562ec9397__af22dc465d:vendors/__SecureComputing/SG560/README
>> <
>> https://gitorious.org/linux-nios2/uclinux-dist/source/5316285bb1b0a07bd2a2a562ec9397af22dc465d:vendors/SecureComputing/SG560/README
>> >
>> >
>> >
>> > Before Linux had in kernel drivers for the IXP4xx eth driver you
>> > had to use Intel's drivers for them. That SecureComputing/SG560
>> > config would have been configured with them in mind. I don't recall
>> > what kernel the Snapgear 4.0 source was based on, but you may be
>> > able to configure and use the kernels own ixp4xx eth drivers.
>> >
>> > You can ignore what that README says about redboot. It doesn't
>> really
>> > apply to the SG560. (The network boot loading is done using a
>> redboot,
>> > but it is a stripped down simple one - that just does the network
>> > loading. It doesn't deal with flash).
>> >
>> > Regards
>> > Greg
>> >
>> >
>> > I would suggest hard setting a command line in your kernel
>> config so that
>> > you have console=ttyS0,115200 set.
>> >
>> > I think I saw an old post on how to do that; if I get past the
>> kernel panic, this will be the first thing I do.
>> >
>> > Regards
>> > Greg
>> >
>> >
>> >
>> > On Mon, Aug 25, 2014 at 9:40 AM, GravyFace <
>> gravyf...@gmail.com <mailto:gravyf...@gmail.com> <mailto:
>> gravyf...@gmail.com <mailto:gravyf...@gmail.com>> <mailto:
>> gravyf...@gmail.com <mailto:gravyf...@gmail.com> <mailto:
>> gravyf...@gmail.com <mailto:gravyf...@gmail.com>>>> wrote:
>> >
>> > Thanks, I'll give that a go now.
>> >
>> >
>> > On Mon, Aug 25, 2014 at 2:24 AM, Greg Ungerer <
>> g...@uclinux.org <mailto:g...@uclinux.org> <mailto:g...@uclinux.org
>> <mailto:g...@uclinux.org>> <mailto:g...@uclinux.org <mailto:
>> g...@uclinux.org> <mailto:g...@uclinux.org <mailto:g...@uclinux.org>>>>
>> wrote:
>> >
>> > Hi,
>> >
>> >
>> > On 24/08/14 03:26, gravyface wrote:
>> >
>> > Hi all,
>> >
>> > First time attempting to compile really
>> anything in Linux (why not try this? <g>), and hitting a wall with a
>> seemingly pam-auth related error.
>> >
>> > Build Environment:
>> >
>> > - Ubuntu Server 12.04.5 LTS with apt
>> versions of binutils, build-essentials, gcc, gdb, curses (libncurses5-dev
>> libncursesw5-dev). I downloaded the arm-linux-tools-20061213.tar.______gz <
>> https://web.archive.org/web/______20100715203220/http://ftp.______snapgear.org/pub/snapgear/______tools/arm-linux/arm-linux-______tools-20061213.tar.gz
>> <
>> https://web.archive.org/web/____20100715203220/http://ftp.____snapgear.org/pub/snapgear/____tools/arm-linux/arm-linux-____tools-20061213.tar.gz>
>> <
>> https://web.archive.org/web/____20100715203220/http://ftp.____snapgear.org/pub/snapgear/____tools/arm-linux/arm-linux-____tools-20061213.tar.gz
>> <
>> https://web.archive.org/web/__20100715203220/http://ftp.__snapgear.org/pub/snapgear/__tools/arm-linux/arm-linux-__tools-20061213.tar.gz>>
>> <
>> https://web.archive.org/web/____20100715203220/http://ftp.____snapgear.org/pub/snapgear/____tools/arm-linux/arm-linux-____tools-20061213.tar.gz
>> > <
>> https://web.archive.org/web/__20100715203220/http://ftp.__snapgear.org/pub/snapgear/__tools/arm-linux/arm-linux-__tools-20061213.tar.gz>
>> <
>> https://web.archive.org/web/__20100715203220/http://ftp.__snapgear.org/pub/snapgear/__tools/arm-linux/arm-linux-__tools-20061213.tar.gz
>> <
>> https://web.archive.org/web/20100715203220/http://ftp.snapgear.org/pub/snapgear/tools/arm-linux/arm-linux-tools-20061213.tar.gz>>>>
>> from Web Archive's copy, but have no idea how to use it.
>> >
>> >
>> >
>> >
>> > I can get whatever versions of packages
>> needed; just let me know.
>> >
>> > Target:
>> >
>> > - I have more SG560s than I know what to
>> do with after dismantling a large site-to-site client network; I'm
>> interested in building simple network testing appliances
>> (ping/arp-scan/nc/ssh) I can use when configuring various networking
>> devices, so I think the default libraries and utilities should be more than
>> adequate in the base image.
>> >
>> > What I've done:
>> >
>> > - Extracted
>> http://ftp.snapgear.org/pub/______snapgear/src/snapgear-4.0.7.______tar.bz2
>> <http://ftp.snapgear.org/pub/____snapgear/src/snapgear-4.0.7.____tar.bz2>
>> <http://ftp.snapgear.org/pub/____snapgear/src/snapgear-4.0.7.____tar.bz2
>> <http://ftp.snapgear.org/pub/__snapgear/src/snapgear-4.0.7.__tar.bz2>> <
>> http://ftp.snapgear.org/pub/____snapgear/src/snapgear-4.0.7.____tar.bz2 <
>> http://ftp.snapgear.org/pub/__snapgear/src/snapgear-4.0.7.__tar.bz2> <
>> http://ftp.snapgear.org/pub/__snapgear/src/snapgear-4.0.7.__tar.bz2 <
>> http://ftp.snapgear.org/pub/snapgear/src/snapgear-4.0.7.tar.bz2>>> to my
>> home directory in a sub-folder called uclinux (full path is
>> /home/gravyface/uclinux/______snapgear-4.0.7). From that directory, ran
>> "make SecureComputing/SG560_default" which ran for 15 minutes or so,
>> happily compiling, until it exited with Error 2, and not a whole lot more:
>> >
>> >
>> >
>> >
>> > By default the build is parallel across the
>> number of CPUs you have.
>> > It may be that the actuall error was way back
>> in the compile output.
>> >
>> > Try running:
>> >
>> > make NON_SMP_BUILD=1
>> SecureComputing/SG560_default
>> >
>> > It will be a lot slower, only running on 1
>> CPU. But it will much
>> > more likely stop at the failure point.
>> >
>> > Regards
>> > Greg
>> >
>> >
>> >
>> > ucfront-gcc arm-linux-gcc -mbig-endian
>> -mcpu=xscale -mtune=xscale -msoft-float -DHOST_NAME_MAX=255 -shared
>> .libs/pam_xauth.o -Wl,--rpath
>> -Wl,/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/libpam/.libs
>> -L/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/libpam
>> /home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/libpam/.libs/libpam.so
>> -mbig-endian -mcpu=xscale -mtune=xscale -msoft-float
>> -Wl,--version-script=../../../______modules/pam_xauth/../____modules.__map
>> -Wl,-S -Wl,-soname -Wl,pam_xauth.so -o .libs/pam_xauth.so
>> > creating pam_xauth.la <http://pam_xauth.la>
>> <http://pam_xauth.la> <http://pam_xauth.la> <http://pam_xauth.la/>
>> > (cd .libs && rm -f pam_xauth.la <
>> http://pam_xauth.la> <http://pam_xauth.la> <http://pam_xauth.la> <
>> http://pam_xauth.la/> && ln -s ../pam_xauth.la <http://pam_xauth.la> <
>> http://pam_xauth.la> <http://pam_xauth.la> <http://pam_xauth.la/>
>> pam_xauth.la <http://pam_xauth.la> <http://pam_xauth.la> <
>> http://pam_xauth.la> <http://pam_xauth.la/>)
>> >
>> > make[8]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/modules/pam_xauth'
>> > make[8]: Entering directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/modules'
>> >
>> >
>> > make[8]: Nothing to be done for `all-am'.
>> > make[8]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/modules'
>> > make[7]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/modules'
>> > Making all in po
>> > make[7]: Entering directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/po'
>> >
>> >
>> > make[7]: Nothing to be done for `all'.
>> > make[7]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/po'
>> > Making all in conf
>> > make[7]: Entering directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/conf'
>> > make[8]: Entering directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/conf'
>> >
>> >
>> > make[8]: Nothing to be done for `all-am'.
>> > make[8]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/conf'
>> > make[7]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build/conf'
>> > make[7]: Entering directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build'
>> >
>> >
>> > make[7]: Nothing to be done for `all-am'.
>> > make[7]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build'
>> > make[6]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build'
>> > make[5]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam/______build'
>> > make[4]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib/libpam'
>> > make[3]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib'
>> >
>> >
>> > make[2]: *** [all] Error 2
>> > make[2]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7/lib'
>> >
>> >
>> > make[1]: *** [subdirs] Error 1
>> > make[1]: Leaving directory
>> `/home/gravyface/uclinux/______snapgear-4.0.7'
>> > make: ***
>> [SecureComputing/SG560_______default] Error 2
>> >
>> >
>> >
>> >
>> > Looks to be pam-related, but with no
>> error, I'm kind of at a loss here.
>> >
>> > Thanks in advance!
>> >
>> >
>> >
>> _____________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>
>> <mailto:uClinux-dev@uclinux. <mailto:uClinux-dev@uclinux.>____org
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>>
>> >
>> http://mailman.uclinux.org/______mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev>> <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>>>
>> > This message was resent by
>> uclinux-dev@uclinux.org <mailto:uclinux-dev@uclinux.org> <mailto:
>> uclinux-dev@uclinux.__org <mailto:uclinux-dev@uclinux.org>> <mailto:
>> uclinux-dev@uclinux. <mailto:uclinux-dev@uclinux.>____org <mailto:
>> uclinux-dev@uclinux.__org <mailto:uclinux-dev@uclinux.org>>>
>> > To unsubscribe see:
>> >
>> http://mailman.uclinux.org/______mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev>> <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>>>
>> >
>> >
>> >
>> _____________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>
>> <mailto:uClinux-dev@uclinux. <mailto:uClinux-dev@uclinux.>____org
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>>
>> >
>> http://mailman.uclinux.org/______mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev>> <
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>>>
>> > This message was resent by
>> uclinux-dev@uclinux.org <mailto:uclinux-dev@uclinux.org> <mailto:
>> uclinux-dev@uclinux.__org <mailto:uclinux-dev@uclinux.org>> <mailto:
>> uclinux-dev@uclinux. <mailto:uclinux-dev@uclinux.>____org <mailto:
>> uclinux-dev@uclinux.__org <mailto:uclinux-dev@uclinux.org>>>
>> > To unsubscribe see:
>> >
>> http://mailman.uclinux.org/______mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev>> <
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>>>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > ___________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>
>> >
>> http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>>
>> > This message was resent by uclinux-dev@uclinux.org
>> <mailto:uclinux-dev@uclinux.org> <mailto:uclinux-dev@uclinux.__org
>> <mailto:uclinux-dev@uclinux.org>>
>> > To unsubscribe see:
>> >
>> http://mailman.uclinux.org/____mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>>
>> >
>> >
>> > ___________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> <mailto:uClinux-dev@uclinux.__org <mailto:uClinux-dev@uclinux.org>>
>> > http://mailman.uclinux.org/____mailman/listinfo/uclinux-dev
>> <http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>>
>> > This message was resent by uclinux-dev@uclinux.org <mailto:
>> uclinux-dev@uclinux.org> <mailto:uclinux-dev@uclinux.__org <mailto:
>> uclinux-dev@uclinux.org>>
>> > To unsubscribe see:
>> > http://mailman.uclinux.org/____mailman/options/uclinux-dev
>> <http://mailman.uclinux.org/__mailman/options/uclinux-dev> <
>> http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>>
>> >
>> >
>> >
>> >
>> > _________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> > http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>
>> > This message was resent by uclinux-dev@uclinux.org <mailto:
>> uclinux-dev@uclinux.org>
>> > To unsubscribe see:
>> > http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>
>> >
>> >
>> > _________________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org <mailto:uClinux-dev@uclinux.org>
>> > http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>
>> > This message was resent by uclinux-dev@uclinux.org <mailto:
>> uclinux-dev@uclinux.org>
>> > To unsubscribe see:
>> > http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > uClinux-dev mailing list
>> > uClinux-dev@uclinux.org
>> > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
>> > This message was resent by uclinux-dev@uclinux.org
>> > To unsubscribe see:
>> > http://mailman.uclinux.org/mailman/options/uclinux-dev
>> >
>>
>> _______________________________________________
>> uClinux-dev mailing list
>> uClinux-dev@uclinux.org
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
>> This message was resent by uclinux-dev@uclinux.org
>> To unsubscribe see:
>> http://mailman.uclinux.org/mailman/options/uclinux-dev
>>
>
>
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
