You'd be able to watch what is actually happening/how much progress is occurring.by WarheadsSE - Debian
ALARM is preparing to integrate as much of the kirkwood family as possible into a single linux-armv5 FDT kernel package, with update u-boots for each device. Glad to see someone has started this.by WarheadsSE - Debian
IIRC either the 320, or the 325 was never actually intended to talk to the OS, and merely does its own thing.by WarheadsSE - Debian
http://www.frys.com/product/6878626 PP Mobile, $4.90 USDby WarheadsSE - Off-Topic
http://archlinuxarm.org/forum/viewtopic.php?f=23&t=7212by WarheadsSE - uBoot
You can also try: echo "0 0 0" > /sys/class/scsi_host/host0/scanby WarheadsSE - Debian
I am pretty I told you exactly why on the ALARM forum there @karolp1993by WarheadsSE - Debian
NP, If you look at my 2.6.31 tree, you will see there is a module that explicitly goes and destroys that damned timer that is set in the u-boot from CE.by WarheadsSE - uBoot
because those instances where it is blinking, it is using a timer & jiffies w/ a shared source file for the definition. See the xce module source code where ti stops the blinky clock.by WarheadsSE - uBoot
The non-dt kernel should have the information for the second sata port near the definitions of the first. I am not sure why you are asking this in the uBoot subforum.by WarheadsSE - uBoot
That product page says: "Dual core CPU at 1.3GHz with 128MB DDR3" That's not a Kirkwood.by WarheadsSE - Debian
I will rebase my NSA3xx branch after that, and get it pulled in.by WarheadsSE - uBoot
The NSA32x series use GPIO's like this for USB & SATA[2] power.by WarheadsSE - Debian
Quoterun to_stock This can be simply executed, as is, from serial, yes. From Linux, you must us fw_setenv. Quote*fan* It's the separate MCU that controls the fan, and its programming. A higher quality fan in the same power envelope should be feasible if you so choose. Quoteoverclock ... 2Ghz Do not attempt. I have had several engineering samples that have cooked themselves after sustaiby WarheadsSE - Debian
Has anyone made an effort to pull from 2013.10 to 2014.1?by WarheadsSE - uBoot
I don't think this belons in u-boot section of the forums.by WarheadsSE - Debian
The Pogoplug Mobile does not have wireless. You will need a dongle.by WarheadsSE - Debian
Bodhi, I would suggest this might be a good idea to include with the u-boot-kirkwood repo builds.by WarheadsSE - uBoot
Because it _can_ be compiled on v5, there is no point in doing it since it can't even be used in such a device.by WarheadsSE - uBoot
I think I need to finish and commit my changes for it before you can compile & test a kwbby WarheadsSE - uBoot
Can it be compiled? Yes. Do you want to do that? No.by WarheadsSE - uBoot
ZFS on a 128MB ram ARMv5 device is a bad choice. Just saying.by WarheadsSE - uBoot
It might not like `mainlineLinux=yes`, but I can't say for sure.by WarheadsSE - uBoot
I might have a NSA310 owning Volunteer to test on.by WarheadsSE - uBoot
Right, I forgot about that move. I can copy default env from any of the other pre-configured ones we already have in this project, of courseby WarheadsSE - uBoot
At this point, I need to put in a sane default environment, and check why it is not seeing the existing environment as valid. Otherwise, as far as I can tell NSA325 & NSA320 are good. I don't have a 310 to try.by WarheadsSE - uBoot
Will do. EDIT: done.by WarheadsSE - uBoot
I have pulled up my NSA320, and it seems to be mostly working with the changes I pulled in. U-Boot 2013.10-g268e791 (Mar 07 2014 - 14:24:23) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 Warning: fby WarheadsSE - uBoot
I can tell you it is an 88F6283by WarheadsSE - uBoot