public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sriramkumar Raju <rsriramkumar@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Adding VIA RHINE driver to i386 platform
Date: Wed, 25 May 2005 12:12:00 -0000	[thread overview]
Message-ID: <7de07eff0505242357741f9477@mail.gmail.com> (raw)
In-Reply-To: <7de07eff05051905235cf39dd8@mail.gmail.com>

Hi,
     I had booted the i386  platform with RedBoot + VIA Rhine Ethernet.
Now while booting i am getting the following message.

Ethernet eth0: MAC address 44:ec:00:00:94:eb
Can't get BOOTP info for device!

RedBoot(tm) bootstrap and debug environment [FLOPPY]
Non-certified release, version UNKNOWN - built 17:29:41, May 24 2005

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000a0000, 0x000897b0-0x000a0000 available
RedBoot>


The MAC address that is being displayed is different from my board MAC address.
 
What i missed while porting the VIA Rhine driver to i386 platform?

Why  i am unable to get the MAC address that is in VIA RHINE controller?


Regards,
Sriram.R


On 5/19/05, Sriramkumar Raju <rsriramkumar@gmail.com> wrote:
> Hi Nick,
>        Do me mean that i have to add Platform specific device
> configurations for VIA RHINE on i386.
> 
> Regards,
> Sriram.R
> 
> On 19 May 2005 09:53:26 +0100, Nick Garnett <nickg@ecoscentric.com> wrote:
> > Sriramkumar Raju <rsriramkumar@gmail.com> writes:
> >
> > >
> > > The build is successful and REDBOOT boots up with a message NO Network
> > > Interface found.
> > >
> > > Also when i open the ecos.ecc that is generated  in GUI based config
> > > tool i can see VIA RHINE support  not enabled.
> > >
> > > when i execute "$./ecosconfig.exe add CYGPKG_DEVS_ETH_VIA_RHINE" it
> > > prompts me that the package is already present.
> > >
> > > Can anyone tell Me what i should do to add VIA RHINE support to i386 platform.
> >
> > In addition to the CYGPKG_DEVS_ETH_VIA_RHINE package you also need to
> > have a package that adapts the generic driver to the specific
> > hardware. Take a look at any of the other PC targets to see how this
> > works. Also take a look at the documentation.
> >
> > The RHINE ethernet driver appears to have only ever been used for the
> > sh7729pci board, so you may have to do a bit of work in the RHINE
> > driver. You should be able to create the new package you need by
> > combining one of the exising PC package with the sh7729pci package.
> >
> >
> >
> > --
> > Nick Garnett                                     eCos Kernel Architect
> > http://www.ecoscentric.com                The eCos and RedBoot experts
> >
> >
>

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2005-05-25  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7de07eff05051805267e5f9d7@mail.gmail.com>
2005-05-19  9:21 ` Sriramkumar Raju
2005-05-19 12:24   ` Nick Garnett
2005-05-19 14:11     ` Sriramkumar Raju
2005-05-19 14:15     ` Sriramkumar Raju
2005-05-19 14:43       ` Gary Thomas
2005-05-25 12:12       ` Sriramkumar Raju [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=7de07eff0505242357741f9477@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).