public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Sriramkumar Raju <rsriramkumar@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Adding VIA RHINE driver to i386 platform
Date: Thu, 19 May 2005 14:43:00 -0000	[thread overview]
Message-ID: <1116506125.22383.109.camel@hermes> (raw)
In-Reply-To: <7de07eff05051905235cf39dd8@mail.gmail.com>

On Thu, 2005-05-19 at 17:53 +0530, Sriramkumar Raju wrote:
> Hi Nick,
>        Do me mean that i have to add Platform specific device
> configurations for VIA RHINE on i386.
> 

Exactly.  Most drivers are divided into a generic portion (the part
that understands the actual device and the work the driver needs to
accomplish) plus a target/platform specific portion (which describes
how the device is configured, addresses, interrupts, and such).  
Depending on the driver, the platform specific portion may come in
the form of an include file or a driver wrapper.  These details are
described by the CDL for the driver.

Look at other platforms which use the RHINE ethernet driver to see
what needs to be done.

> 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
> > 
> >

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


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

  reply	other threads:[~2005-05-19 12:36 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 [this message]
2005-05-25 12:12       ` 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=1116506125.22383.109.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=rsriramkumar@gmail.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).