dockstar support will be in next linux kernel

Patches to support the dockstar (basically: machine ID and LEDs) were merged into the linux-2.6-stable tree at kernel.org recently.

Great work, Eric!

Even better is the fact that Dockstar support is already included in the latest Debian kernels.

-- Jeff

Jeff Wrote:
-------------------------------------------------------
> Great work, Eric!
>
> Even better is the fact that Dockstar support is
> already included in the latest Debian kernels.
>
> -- Jeff


not in the next five years ;-) debian is soooooooooooooooooooooooo slow

In the last kirkwood update or two, the changelog has the following:

* ARM: update mach types.
* [armel/config.kirkwood] Enable MACH_DOCKSTAR.

I haven't rebooted, so I can't say exactly what that does. But google for MACH_DOCKSTAR, and you find a patch by ecc, here.

After you install the new kernel package, make sure you update the arcNumber variable in uBoot. By default, it will use the overloaded Sheevaplug ID. To use a kernel with official Dockstar support, you need to have the latest uBoot and then run

fw_setenv arcNumber 2998

-- Jeff

I hadn't known about that step, thanks. Is the newest uBoot really necessary? I'm deathly afraid of flashing while I've got a working setup.... :-)

Yes. Only the newest uBoot has support for the arcNumber variable.

Bother. How do we flash again, by just running http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh? It's been a while for me:

233% uptime
 20:16:14 up 30 days, 23:50,  8 users,  load average: 0.00, 0.02, 0.00

And can it be flashed while running Debian, or must I go into the native environment?



Edited 1 time(s). Last edit at 10/27/2010 07:18PM by ayrlander.

Yes, all you have to do is download and run the installer. It works fine in Debian.

Yay. Flashed and nothing bad happened. And my LED works out of the box. :-)

Only weird thing was, before I rebooted, I ran "fw_setenv rootfstype ext3" to reset that, since after flashing I saw it had gotten reset to ext2. But, after rebooting, it's back to ext2, and that's how / is mounted. Except I just now noticed it should be usb_rootfstype. Oops. So now I have a rootfstype and a usb_rootfstype in my fw_printenv. And no fw_unsetenv command. :-)

May that be my biggest problem I have with my Dockstar....