This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: config restrictions in i82559 driver
- From: "Gary D. Thomas" <gary dot thomas at mind dot be>
- To: Mark Salter <msalter at redhat dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 09 Feb 2003 10:01:30 -0700
- Subject: Re: [ECOS] config restrictions in i82559 driver
- References: <20030207185950.A88467884D@deneb.localdomain>
On Fri, 2003-02-07 at 11:59, Mark Salter wrote:
> if_i82559.c has these restrictions in place:
>
> #ifdef CYGHWR_DEVS_ETH_INTEL_I82559_GET_ESA
> #ifndef CYGHWR_DEVS_ETH_INTEL_I82559_HAS_NO_EEPROM
> #error This platform has EEPROM, yet external ..._GET_ESA is defined
> #endif
> #endif
>
> #ifdef CYGHWR_DEVS_ETH_INTEL_I82559_GET_ESA
> #ifdef CYGHWR_DEVS_ETH_INTEL_I82559_HAS_ONE_EEPROM
> #error This platform has one EEPROM, yet external ..._GET_ESA is defined
> #endif
> #endif
>
> I think this is overly restrictive. Basically, I have a situation
> where I want the ESA settable through RedBoot's fconfig command
> even though an EEPROM is present. I also want the driver to write
> the ESA into EEPROM so that linux will pick it up. Is there any
> reason not to remove the above restrictions?
Not at all, as long as the result can be easily manipulated via
the CDL. The restrictions as they exist are from Hugo's work
with these devices and are just a reflection of his experiences.
--
.--------------------------------------------------------.
| Mind: Embedded Linux and eCos Development |
|--------------------------------------------------------|
| Gary Thomas email: gary.thomas@mind.be |
| Mind ( http://mind.be ) tel: +1 (970) 229-1963 |
| gpg: http://www.chez-thomas.org/gary/gpg_key.asc |
'--------------------------------------------------------'
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss