Re: More Sandpoint woes

3 messages, 3 authors, 2000-09-07 · open the first message on its own page

Re: More Sandpoint woes

From: Alex Shnitman <hidden>
Date: 2000-09-06 21:32:36

Hi, Mark!

On Tue, Sep 05, 2000 at 03:40:13PM -0700, you wrote the following:
Alex, if you're interested, I have a better kernel for you to use.  Its in
ftp://www.mvista.com/pub/Area51/sandpoint-8240/sandpoint.linux.tar.gz
Thanks! This did get me further. No more oddities with the
ramdisk/initrd options, and it doesn't crash when trying to run init
-- but instead, it just hangs.. Right after the message "Freeing
unused kernel memory", there's nothing more on the screen. The console
works (when I type something I get it echoed back), and the machine is
pingable, but it just doesn't seem to do anything. Running sash
instead of init yields the same thing.

I wanted to try to debug this myself, because I feel it must be
something not very complicated. But without kgdb I can't do anything.
So I tried to make kgdb work with the Sandpoint. From what I see, the
kgdb-enabled kernel for ppc has the functions getDebugChar,
putDebugChar and kgdb_interruptible in macserial.c, however Sandpoint
uses the regular serial.c, so I don't have these functions and thus
linking fails. Therefore I figured that I should find a kgdb patch for
i386 that would put such funtions into serial.c. I intend to do that
tonight. If you have other tips for me, I'll be delighted to hear.
How do *you* debug it anyway?

Also, I'm confused a bit about -msoft-float and -mhard-float. The 7400
has an FPU, so is it right that the kernel compiles itself with
-msoft-float?
This has IDE support
Why wouldn't the standard Linux IDE support work? Or are we talking
about different levels here? (Are you talking about some
initialization that is needed for the regular IDE code to work or
something like that? Just a guess...)
and fixes a bug in the eepro100.c driver for the sandpoint.
Ooh! I selected the eepro100 because I thought that'd be the most
reliable -- I also have an RTL8129 here, and some no-name card that's
supported by tulip.c. Was eepro100 the wisest choice, or should I take
another card? Actually, it probably doesn't really matter once it's
working..

And Mark -- thanks a lot! I don't know where I'd be today if it wasn't
for your help.


--
Alex Shnitman                            | http://www.debian.org
alexsh@hectic.net, alexsh@linux.org.il   +-----------------------
http://alexsh.hectic.net    UIN 188956    PGP key on web page
       E1 F2 7B 6C A0 31 80 28  63 B8 02 BA 65 C7 8B BA

Ambition is a poor excuse for not having enough sense to be lazy.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: More Sandpoint woes

From: Bob Doyle <hidden>
Date: 2000-09-07 04:09:41

Alex Shnitman wrote:
Hi, Mark!
[snip]
Ooh! I selected the eepro100 because I thought that'd be the most
reliable
[snip]

I was about to ask the same question...  I didn't see a list of
known-to-work
network cards.  Right now my Sandpoint has a AMD Lance card in it.  Will
that
work?

Bob

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: More Sandpoint woes

From: Mark A. Greer <hidden>
Date: 2000-09-07 17:12:59

Alex, Bob,

I expected the eepro100 driver to just work too.  What I found, though, was
that one of the writes to a register was being byte-swapped twice (once
explicitly in the call to outl() and again by outl()).  I changed it to swap
once and things worked much better.

I haven't been following the changes to this driver so I don't know how often
it gets modified.  My assumption at the time was that someone had recently
modified the driver and no one had since tested it on a big-endian machine.
When I get ready to integrate with the latest src base, I'll sort through it
all again.

I think the 8255x enet ctlr is still a good choice.

Bob, I don't know about your AMD card, I haven't tried it.

A note to everyone, for whatever reason(s), the sandpoint has been a difficult
platform to get things to work.  Lots of things that should "just work",
don't.  I've tested with 82559 and 8139 ethernet ctlrs.  They worked for me
with the kernel you now have.  I encountered trouble (timing issues, etc) at
many steps along the way; don't be surprised if you do too.  Sounds like you
guys are taking it beyond where I took it so don't expect an easy ride.  Just
speaking from experience...  :(

Mark
--

Bob Doyle wrote:
Alex Shnitman wrote:
quoted
Hi, Mark!
[snip]
quoted
Ooh! I selected the eepro100 because I thought that'd be the most
reliable
[snip]

I was about to ask the same question...  I didn't see a list of
known-to-work
network cards.  Right now my Sandpoint has a AMD Lance card in it.  Will
that
work?

Bob
--
Mark A. Greer (mgreer@mvista.com; 480-517-0287)
MontaVista Software, Inc.
2141 E. Broadway Road, Suite 108
Tempe, AZ  85282


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help