I was just about to start a new thread about the impeding DTopcalypse, but then remembered this one. So, short story: I have my GoFlex Net booting 3.5 via Device Tree. It's including in linux-next now and should be showing up formally in 3.6. Kirkwood DT support has gotten much better, pretty much everything can be defined via GPIO now, about the only holdout is ethernet but that'by Kurlon - Debian
Older topic, but seeing as I've been playing with this extensively I figure it's due for an update. First, tsunulukai the screen flickering you're seeing is due to the way displaylink devices work in kernels older than 3.3 or so. The udlfb driver is maintaining a shadow buffer in ram, and IIRC uses page faults to determine when a section of that FB has changed. On a change thaby Kurlon - Debian
davygravy Wrote: ------------------------------------------------------- > Hmmm... that may be something related to ALARM in > particular. I built a Buildroot image last night > w/ 3.4.1 and it was fine - I did check reboot and > halt - both worked as expected. I haven't tried > it in Debian, but if it works in Buildroot, then > it should prolly be ok in Debian.by Kurlon - Debian
This is where I'm at trying to get 3.5rc3 to cooperate. You also have to apply a printk fix to get 3.5 to work on kirkwood systems FYI. Anyone spot anything obviously wrong in my hack? diff -ruN a/arch/arm/boot/dts/kirkwood-goflexnet.dts b/arch/arm/boot/dts/kirkwood-goflexnet.dts --- a/arch/arm/boot/dts/kirkwood-goflexnet.dts 1969-12-31 19:00:00.000000000 -0500 +++ b/arch/arm/boot/dby Kurlon - Debian
Welp, I can get the kernel to load and init... but then it just stops, never mounts a rootfs or complain about not having one specified. Not sure how to proceed, was really hoping it was just going to work. :Dby Kurlon - Debian
Yeah, the crew on that list so far seems VERY helpful. I'm starting a second test build of 3.5-rc2 on my GFN, including a patch to fix printk induce early boot hangs as was kindly pointed out as needed on the list. If this works I'll have a nice template to abuse for bootstrapping the rest of the plug family.by Kurlon - Debian
There are a few kirkwoods defined, the Iomega Iconnect, Dreamplug and a couple Dink NAS boxes. None of them have GPIO based devices defined yet, or SATA/Ethernet so I'm not 100% positive they are fully functional yet. I'm still digging through the list archives to find out what the status of things are at the moment.by Kurlon - Debian
I've moved into crazy-land. I've subscribed to the linux-arm-kernel list and will be seeing if I can get some guidance from there on getting the GFN working with the new device tree support being baked in for Kirkwood devices. I suspect once I know enough to get the GFN rolling, the other kirkwood devices should be cake to port over, and even better should be quick to get supported diby Kurlon - Debian
The newer kernels bring a few improvements of note for plug users: 1) Improved udlfb / fbcons modules - I'm doing 720x480@25fps video out of my GoFlex Net via a USB video adapter, as the modules improve so should that performance. Need to be on 3.3 to really see the gains so far. 2) zram support - It's present in older kernels but... slow. New compression options are present thaby Kurlon - Debian
I'm feeling foolish, i'm going to take a stab at writing a GFN entry and doing up a 3.5 kernel to see what happens. Just looking at those files makes my eyes cross but I think I can at least scratch out enough of a file to get booting.by Kurlon - Debian
I'm running 3.4.1 with a hacked up set of ArchLinux ARM patches. So far the only fault I can find is it doesn't reboot on it's own. The kernel halts, but never kicks the GFN over. 3.4 did the same thing...by Kurlon - Debian
davygravy Wrote: > 2. Are you saying that your 3.4 boots but > reboot does not behave has > expected? > (FWIW, 3.4.1 is just out...) Correct, runs beautifully, if I shutdown -h -P it powers down like I'd expect, but if I reboot it spits out "Restarting System.", turns the status LED off, and just sits there. I have to yank the power to get it to boot agby Kurlon - uBoot
I can confirm the new uboot does not hang with my USB dock plugged in at power up any more on my GFN. Now if I can just figure out why 3.4 hangs at reboot... :Dby Kurlon - uBoot
Just to verify, the suggested update method is to snag http://projects.doozan.com/uboot/install_uboot_mtd0.sh and let it do the dirty work? Will it preserve my bootenv or will I have to reset that info again?by Kurlon - uBoot
I'll give it a go Monday as my setup is at work, suspect it'll balk as it always shows as a hub, it's just the video device off the hub that starts off identifying as a mass storage device... really annoying design unless you're running Windows really. Oh, I now have serial access too so I'll be able to capture better debug info now.by Kurlon - uBoot
I can give it a try, although that will introduce new issues with the displaylink interface down the line as the keyboard's hub is only 1.1 and udlfb doesn't like usb 1.1. :D The cables are new, once fired up I'm saturating the usb bus fairly constantly doing video over the link with no errors that I can see. I'll have to poke to see if there are any error counters hiding inby Kurlon - uBoot
In my case, no further output, no other signs of activity or life after 'scanning for storage devices...' The dock has 5 USB ports off it's internal hub, my keyboard has it's own hub with two more ports. I've tried booting booting with just the wifi or keyboard plugged into the GFN, no issues. Any combination of devices off the dock results in the same hang if itby Kurlon - uBoot
Unfortunately because the GFN only has one USB port, I'm limited in how I can setup the topology. GFN to dock, my keyboard and wifi adapter hang off the dock's hub, as do the dock's sound, video (mass storage till you change it's profile number), and ethernet interface. I think I'm the only nutball foolish enough to try using a GFN as a full workstation, I don'tby Kurlon - uBoot
http://pastie.org/3998285 So this is my current stumbling block. If I plug in my Kensington dock and power up the GFN, I get the EHCI time out and then it hangs at scanning the bus. The dock is a bit of a PITA as the displaylink device in it initially comes up looking like a mass storage device. With Jeff's original u-boot and the arch env the scan would complete, it would then try tby Kurlon - uBoot
Seems whatI'm missing is hd_args_0 and hd_args_1 and I can't seem to set them correctly from uboot. What I had before: hd_args_0=boot_dev='ide 0:1'; dev_args='root=/dev/sda1' hd_args_1=boot_dev='ide 1:1'; dev_args='root=/dev/sdb1' I can't seem to coax setenv to get those internal apostrophes to stick. Edit: With a lil manual coaxby Kurlon - uBoot
Got the new uBoot installed, but now I can't fire up any of my archlinux media. I suspect I typo'd something when recreating the env. I have working netconsole access, and tftload functionality in uBoot. Whenever I try to launch a kernel all life stops at "Starting kernel ..." with no signs of activity after, including zilch from the NIC watching with tcpdump. Any suggestiby Kurlon - uBoot
Bah, wrong thread, sorry...by Kurlon - Rescue System