public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: How to activate ethernet driver
Date: Fri, 10 Apr 2015 14:30:00 -0000	[thread overview]
Message-ID: <mg8mpa$i9b$1@ger.gmane.org> (raw)
In-Reply-To: <CABmKEG_ROBRn8eofK3U7igUd=m5tHzt1YHHF8N2OvqqX5zK89w@mail.gmail.com>

On 2015-04-10, Jerzy Dyrda <jerzdy@gmail.com> wrote:
> Hello Dennis,
>
> 2015-04-10 11:11 GMT+02:00  <Incubus84@web.de>:
> [snip]
> We are a bit closer.

>> I digged a little deeper in the source code and found the function
>> "cyg_io_init" which iterates over the __DEVTAB__ table. I can see how
>> it runs through different devices like tty, flash, adc, ... but not
>> the ethernet driver. As far as I understand the reference manual,
>> this SHOULD happen here too!
>
> No exactly, it seems that Ethernet driver is a different sort of
> devices strictly connected to network stack.

[...]

True.  However, you can create a "normal" driver table entry for an
Ethernet driver if you want to.

Then you can have an init function called exactly once at system
startup time.

You can also then use use cyg_io_read(), cyg_io_write(),
cyg_io_set_config(), cyg_io_get_config() etc. for whatever you want.
I've done that in the past for a number of Ethernet drivers so that
user application can read/write raw MAC-level packets for certain
proprietary Ethernet protocols. [The eCos network stacks didn't used
to provide any mechanism for that].  We also use the normal cyg_io API
to allow application code to configure and uery a variety of features
in the Ethernet controller hardware that the normal network stacks are
not aware of and for which they provide no API.

-- 
Grant Edwards               grant.b.edwards        Yow! Don't hit me!!  I'm in
                                  at               the Twilight Zone!!!
                              gmail.com            


-- 
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:[~2015-04-10 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 21:10 [ECOS] " Dennis S
2015-04-09 12:15 ` Jerzy Dyrda
     [not found]   ` <trinity-4777fcb7-729d-4f01-bb84-58b445200f13-1428584884951@3capp-webde-bs37>
2015-04-09 13:43     ` Jerzy Dyrda
     [not found]       ` <trinity-88db4679-45f1-4bed-85a9-70b78399a50a-1428657096995@3capp-webde-bs01>
2015-04-10 11:26         ` Jerzy Dyrda
2015-04-10 14:30           ` Grant Edwards [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='mg8mpa$i9b$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).