In message: <[EMAIL PROTECTED]>
Brenden Grace <[EMAIL PROTECTED]> writes:
: On Wed, 2004-09-29 at 15:32, Peter Buckingham wrote:
: > experience then just not compiling in the em driver or an ugly like i
: > describe (or you suggest) should be fine.
:
: I wasn't trying to be rude, bu
In message: <[EMAIL PROTECTED]>
Brenden Grace <[EMAIL PROTECTED]> writes:
: On Wed, 2004-09-29 at 13:37, Peter Buckingham wrote:
: > why compile the em driver in at all? it won't probe the device if it
: > doesn't exist ;-)
:
: because I need it ...
As opposed to just hacking the em
In message: <[EMAIL PROTECTED]>
Brenden Grace <[EMAIL PROTECTED]> writes:
: I am writing a network driver for a em(4) compatible chip. I know the
: specific subvendor id and subdevice id, but the em(4) driver seems to
: attach to the device before my driver can. Is this because the em_p
On Wed, 2004-09-29 at 15:32, Peter Buckingham wrote:
> experience then just not compiling in the em driver or an ugly like i
> describe (or you suggest) should be fine.
I wasn't trying to be rude, but DEVICE_PROBE(9) seems to describe how
conflicts like this should be handled. I was wondering i
On Wed, 2004-09-29 at 13:37, Peter Buckingham wrote:
> why compile the em driver in at all? it won't probe the device if it
> doesn't exist ;-)
because I need it ...
> otherwise, just add some code to the em's probe routine to check for
> your subvendor, subdevice pair and exit without attachin
On Wed, 2004-09-29 at 13:00, Steven Hartland wrote:
> If its compatible with em why not just alter the em to support
> the additional id's?
Because I don't need to ...
Me:
> > but the em(4) driver seems to attach to the device before my driver
> > can.
This card works fine with the em driver, b
If its compatible with em why not just alter the em to support
the additional id's?
Steve
- Original Message -
From: "Brenden Grace" <[EMAIL PROTECTED]>
I am writing a network driver for a em(4) compatible chip. I know the
specific subvendor id and subdevice id, but the em(4) driver s
I have a somewhat limited knowledge of FreeBSD's device system, so
forgive (and correct) me if I get any of this wrong.
I am writing a network driver for a em(4) compatible chip. I know the
specific subvendor id and subdevice id, but the em(4) driver seems to
attach to the device before my driver
8 matches
Mail list logo
