In message <19990714185101.09...@goatsucker.org> Scott Mitchell writes:
: Ugh. In that case, can someone back out Poul-Henning's changes to the
: if_xe.c in the -STABLE tree? That's (I hope) the only thing stopping it
: from working. At least that way only my code will be bogus :-) Believe
: me
In message <[EMAIL PROTECTED]> Scott Mitchell writes:
: Ugh. In that case, can someone back out Poul-Henning's changes to the
: if_xe.c in the -STABLE tree? That's (I hope) the only thing stopping it
: from working. At least that way only my code will be bogus :-) Believe
: me, I know it's ugl
In message <19990714185101.09...@goatsucker.org>, Scott Mitchell writes:
>Ugh. In that case, can someone back out Poul-Henning's changes to the
>if_xe.c in the -STABLE tree?
Uhm my change has not been applied to STABLE, but the 3.2-PAO import
references current rather than stable.
--
Poul-Henni
On Wed, Jul 14, 1999 at 12:52:38AM -0600, Warner Losh wrote:
> In message <19990713182203.a68...@nuxi.com> "David O'Brien" writes:
> : Since no one has repsonded to this querry, I will be un-staticizing these
> : so they will be available to drivers.
>
> No. Please don't. This is the first I've
In message <[EMAIL PROTECTED]>, Scott Mitchell writes:
>Ugh. In that case, can someone back out Poul-Henning's changes to the
>if_xe.c in the -STABLE tree?
Uhm my change has not been applied to STABLE, but the 3.2-PAO import
references current rather than stable.
--
Poul-Henning Kamp
On Wed, Jul 14, 1999 at 12:52:38AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "David O'Brien" writes:
> : Since no one has repsonded to this querry, I will be un-staticizing these
> : so they will be available to drivers.
>
> No. Please don't. This is the first I've seen this.
In message <19990713210337.h85...@remarq.com> Ade Lovett writes:
: This is going to be for both -current and MFC'd back into -stable, yes?
The interface for doing this I'll be merging back into -stable.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers"
In message <19990713182203.a68...@nuxi.com> "David O'Brien" writes:
: Since no one has repsonded to this querry, I will be un-staticizing these
: so they will be available to drivers.
No. Please don't. This is the first I've seen this. There will be
another cis reading interface as part of the
In message <[EMAIL PROTECTED]> Ade Lovett writes:
: This is going to be for both -current and MFC'd back into -stable, yes?
The interface for doing this I'll be merging back into -stable.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of th
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: Since no one has repsonded to this querry, I will be un-staticizing these
: so they will be available to drivers.
No. Please don't. This is the first I've seen this. There will be
another cis reading interface as part of the newbusificat
On Tue, Jul 13, 1999 at 06:22:03PM -0700, David O'Brien wrote:
> [about cdread()/cdwrite() in /sys/pccard/pcccard.c]
>
> Since no one has repsonded to this querry, I will be un-staticizing these
> so they will be available to drivers.
This is going to be for both -current and MFC'd back into -sta
> The Xircom ethernet driver needs to read/write PCCARD attribute memory from
> its probe routine, in order to identify the type of card and to beat
...
> then making crdread() and crdwrite() (in /sys/pccard/pccard.c)
> non-static and calling them directly from the driver code would be an
> easy w
On Tue, Jul 13, 1999 at 06:22:03PM -0700, David O'Brien wrote:
> [about cdread()/cdwrite() in /sys/pccard/pcccard.c]
>
> Since no one has repsonded to this querry, I will be un-staticizing these
> so they will be available to drivers.
This is going to be for both -current and MFC'd back into -st
> The Xircom ethernet driver needs to read/write PCCARD attribute memory from
> its probe routine, in order to identify the type of card and to beat
...
> then making crdread() and crdwrite() (in /sys/pccard/pccard.c)
> non-static and calling them directly from the driver code would be an
> easy
Hi all,
The Xircom ethernet driver needs to read/write PCCARD attribute memory from
its probe routine, in order to identify the type of card and to beat
brain-damaged CEM56 cards into shape :-) Currently this is done by way of
'fake' calls to read() and write() on the appropriate /dev/cardXX dev
Hi all,
The Xircom ethernet driver needs to read/write PCCARD attribute memory from
its probe routine, in order to identify the type of card and to beat
brain-damaged CEM56 cards into shape :-) Currently this is done by way of
'fake' calls to read() and write() on the appropriate /dev/cardXX de
16 matches
Mail list logo
