On Tue, 28 Sep 2004 16:22:29 -0700
Jerry Toung [EMAIL PROTECTED] wrote:
Hi Greg,
thank you for all the feedback. The set remotebaud 1 thing in my
previous email was a typo, I usually enter 9600.
So you're saying that I may have a communication problem. I would like
to point out that I can
On Fri, Sep 24, 2004 at 10:37:54PM +, Christian S.J. Peron wrote:
Good day folks, we need some beta testers
Hi, as an author of LOR reports I feel obliged to test this patch. I was
running it for a 2 days and intended to report, that for me everything works
ok, when an panic occured.
Hello, World!
Opening a remote HTTP URL in raplayer (old a.out program) makes my
FreeBSD 4.10-RELEASE box completely frozen. The system does not respond
on PINGs. The same happens when I run raplayer in a remote X session. It
looks like the trouble happens in the beginning of the
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
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
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, but 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 attaching.
Is it possible to use the same serial line as the console and GDB port? I
currently have console=comconsole in my loader.conf and am able to break
to the debugger in tip. (I'm Ssh'ing into a box connected via serial line
to the dev box.) I tried setting up gdb on that serial link. Broke into
the
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 if
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
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:
: 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
12 matches
Mail list logo
