public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jim Bradleigh <jim.bradleigh1@btinternet.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: John Dallaway <john@dallaway.org.uk>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Ethernet controllers..
Date: Mon, 24 Aug 2009 15:59:00 -0000	[thread overview]
Message-ID: <885866.27562.qm@web87008.mail.ird.yahoo.com> (raw)
In-Reply-To: <4A92B2B2.8080301@mlbassoc.com>

Hi Gary,

If bring up the network cards using my own processes (as I currently do with a "custom" RTK 8139 driver) how would I go about replacing the udelay's with a more thread friendly process? Just a matter of "cyg_thread_delay" instead?

As previous described I only use eth0 with the FreeBSD stack, the other two ethernet ports are spoke to directly by my application and I just want to avoid any pitfall early on when I have to brief the powers that be in my work...

Thanks,

Jim



----- Original Message ----
From: Gary Thomas <gary@mlbassoc.com>
To: Jim Bradleigh <jim.bradleigh1@btinternet.com>
Cc: John Dallaway <john@dallaway.org.uk>; ecos-discuss@ecos.sourceware.org
Sent: Monday, 24 August, 2009 4:33:06 PM
Subject: Re: [ECOS] Re: Ethernet controllers..

Jim Bradleigh wrote:
> Hi John,
> 
> Thanks for the update, I`m currently using RTL8139 based cards but my project requires alot of performance from the network elements and eventually Gigabit Ethernet..
> 
> In this reguard I`ll have to look into Intel cards sooner or later, can anyone tell me why the Intel 82544 driver uses the function "udelay" alot - I`m concerned that the udelay is a hardware delay which will prevent threads (or other 82544 cards in the system) from running.

None of the uses of udelay are in the main processing path - only
during initialization.

> ----- Original Message ----
> From: John Dallaway <john@dallaway.org.uk>
> To: Jim Bradleigh <jim.bradleigh1@btinternet.com>
> Cc: ecos-discuss@ecos.sourceware.org
> Sent: Monday, 24 August, 2009 1:35:09 PM
> Subject: [ECOS] Re: Ethernet controllers..
> 
> Hi Jim
> 
> Jim Bradleigh wrote:
> 
>> Thought I would throw this out to the list to see if anyone can help...
>>
>> As everyone know's eCos supports a limited device driver list for each
>> platform, I`m currently running on i386 which limits me to a real-tek
>> and two Intel chipsets...
>>
>> Where do most of you purchase network controllers from?
> 
> The easiest route is probably a D-Link DFE-530TX+ PCI card which uses
> the RTL8139 part and can be found via Amazon in the UK.
> 
>> I can`t find
>> any network cards which say they contain the Intel i82544 chipset.. It
>> would be nice to start my project with a defined hardware spec that I
>> know I can purchase..
> 
> The i82544 featured on the Intel Pro/1000 ethernet card which appears to
> have been replaced by the Pro/1000 GT card:
> 
> http://www.intel.com/products/desktop/adapters/pro1000gt/pro1000gt-overview.htm
> 
> The newer card uses the i82541 part which may or may not be compatible.
> 
>> One other question, does anyone know if a network card with the Marvell
>> 88E1111 chipset exists?
> 
> The 88E1111 is an ethernet PHY (transceiver), not a controller.
> 
> I hope this helps.
> 
> John Dallaway
> 


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

--
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:[~2009-08-24 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  8:12 [ECOS] eCos problem: if_lancepci.c does not compile for i386 (vmWare) Waskita Adijarto
2009-08-24 11:36 ` [ECOS] Ethernet controllers Jim Bradleigh
2009-08-24 12:35   ` [ECOS] " John Dallaway
2009-08-24 15:23     ` Jim Bradleigh
2009-08-24 15:33       ` Gary Thomas
2009-08-24 15:59         ` Jim Bradleigh [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=885866.27562.qm@web87008.mail.ird.yahoo.com \
    --to=jim.bradleigh1@btinternet.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    --cc=john@dallaway.org.uk \
    /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).