From: Sriramkumar Raju <rsriramkumar@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Issue with VIA Rhine II ethernet Driver on I386 platform in latest code base.
Date: Tue, 12 Jul 2005 10:34:00 -0000 [thread overview]
Message-ID: <7de07eff0507120332361df98e@mail.gmail.com> (raw)
Hi,
I had ported RedBoot to i386 platform having VIA Rhine II
Ethernet controller. It is working well with the code base that I got
from "http://safariexamples.informit.com/0130354732/".
I took the latest eCOS code base from
"http://ecos.sourceware.org/anoncvs.html" by executing the command
"cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P
ecos".
I did the porting of the VIA Rhine driver to the i386 platform in
latest code base. The system failed to boot. So i tried to debug it by
enabling the DEBUG in Rhine driver and some more diag_printf
statements. So after adding debug I got the system booting and got
DHCP ip address from the DHCP server. I am able to telnet to the
target.
I want to know what might be reason that makes my system to come up
once I add the debug message. Do I need to change the memory
configuration of my system while porting the driver to i386 platform?
Does any one faced similar problem. What I forgot to do while porting
VIA Rhine to i386 platform? Does any one know what is needs to be done
while porting any driver to RedBoot or ECOS platform on i386 target.
Kindly help me if anyone aware of this issue.
Regards,
Sriram.R
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-07-12 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 10:34 Sriramkumar Raju [this message]
2005-07-12 11:38 ` Andrew Lunn
2005-07-14 7:45 ` Sriramkumar Raju
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=7de07eff0507120332361df98e@mail.gmail.com \
--to=rsriramkumar@gmail.com \
--cc=ecos-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).