Poul,
Thanks for the advice! What I tried doing was to make a simple change in
geode.c as follows:
$ diff geode.c geode.c.original
46c46
< { "net5", 0, 8 }, /* net5xxx */
---
> { "net4", 0, 8 }, /* net45xx */
--------------
Also, for a sanity check, my NET4X_5X configuration starts as follows:
machine i386
#cpu I486_CPU
cpu I586_CPU # Compatible w/ net48xx & net55xx
#cpu I686_CPU
ident NET4X_5X
options CPU_GEODE
options CPU_SOEKRIS
...
Unfortunately, after the doing the make (on my deployment server, not the
Soekris) and installing the kernel in the 5501, I still don't have a /dev/led.
Is there more to it than this? Also, if you are wondering why I called the
config NET4X_5X, my original hack to geode.c was to recognize both "net4" and
"net5" strings. While it compiled and booted fine, I didn't see /dev/led, so I
went w/ a very very simple mod as you see in the diff above.
-tm
________________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Poul-Henning Kamp [EMAIL
PROTECTED]
Sent: Saturday, August 25, 2007 2:53 AM
To: Tom Mazzotta
Cc: [email protected]
Subject: Re: [Soekris] Controlling Error LED's on 5501
In message <[EMAIL PROTECTED]>, Tom Mazzotta writes:
>I would like to use the led command to control the red error led
>>on the 5501. I have compiled my kernel w/ the "options CPU_GEODE"
>and "options CPU_SOEKRIS" directives. However, the system does not
>recognize a /dev/led/error device. What else needs to be done for
>the system to recognize this device?
The bios recognition string in src/sys/i386/i386/geode.c needs updated
to find the 55xx series also.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
