From: Matej Kupljen <matej.kupljen@ultra.si>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: bdi2000 debugging
Date: Thu, 17 Feb 2005 10:53:32 +0100 [thread overview]
Message-ID: <1108634012.2801.8.camel@mbmatejdebian.ultra.si> (raw)
In-Reply-To: <4213DAEE.5000802@246tNt.com>
Hi
> L25R marking on the top means rev 1.2 IIRC. That's the one I have. Also,
> if you have a
> rev 2, you're lucky, I'd like one ;)
Nope, mine has: 2L25R
So
> Serial port console is OK the drivers I know don't use bestcomm. But
> USB, Ethernet, IDE, Codec, ....
O.K.
I need Ethernet, because I use NFS rootfs :-(
Thanks for the info.
BR,
Matej
prev parent reply other threads:[~2005-02-17 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 9:50 bdi2000 debugging Matej Kupljen
2005-02-16 10:15 ` Hans Thielemans
2005-02-16 12:06 ` Stefan Nickl
2005-02-16 12:20 ` Matej Kupljen
2005-02-16 20:55 ` Sylvain Munaut
2005-02-16 21:21 ` Matej Kupljen
2005-02-16 23:44 ` Sylvain Munaut
2005-02-17 9:53 ` Matej Kupljen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1108634012.2801.8.camel@mbmatejdebian.ultra.si \
--to=matej.kupljen@ultra.si \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tnt@246tNt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).