>
> BTW: will the new shim solve the issue that on my tecra8000 the PCI:PCIC
> controller gets an shared interupt with other PCI controllers which I can not
> use with the former pccard code.
huh?
my tecra8000 works great with a linksys 10/100 pcmcia card.
my problem is
It seems Soren Schmidt wrote:
> It seems Doug Rabson wrote:
> > >
> > > Hmm, I'm also having a hell of a time here, on closer inspection it
> > > turns out that my problem is that the kernel allways finds an ed0
> > > device allthough none is present. I have both an ed0 & an ep0 device
> > > in m
On Wed, 8 Sep 1999, Matthew N. Dodd wrote:
> On Wed, 8 Sep 1999, Soren Schmidt wrote:
> > Hmm, I'm also having a hell of a time here, on closer inspection it
> > turns out that my problem is that the kernel allways finds an ed0
> > device allthough none is present. I have both an ed0 & an ep0 dev
It seems Doug Rabson wrote:
> >
> > Hmm, I'm also having a hell of a time here, on closer inspection it
> > turns out that my problem is that the kernel allways finds an ed0
> > device allthough none is present. I have both an ed0 & an ep0 device
> > in my config as I use both type of cards. So m
On Tue, 7 Sep 1999, Warner Losh wrote:
...
> Fix the resource allocation error. :-) That's really the only way
> that you'll be able to fix it.
Hmm.
Why should just upgrading the kernel and not changing the configuration/hardware
give me an resource conflict?
BTW: will the new shim solve the iss
On Wed, 8 Sep 1999, Soren Schmidt wrote:
> It seems Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Michael
>Reifenberger writes:
> > : if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
> >
> > The ep driver works in -current.
> >
> > : The message from pccard
It seems Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Soren Schmidt writes:
> : Hmm, I'm also having a hell of a time here, on closer inspection it
> : turns out that my problem is that the kernel allways finds an ed0
> : device allthough none is present. I have both an ed0 & an ep0 device
On Wed, 8 Sep 1999, Soren Schmidt wrote:
> Hmm, I'm also having a hell of a time here, on closer inspection it
> turns out that my problem is that the kernel allways finds an ed0
> device allthough none is present. I have both an ed0 & an ep0 device
> in my config as I use both type of cards. So m
In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: Hmm, I'm also having a hell of a time here, on closer inspection it
: turns out that my problem is that the kernel allways finds an ed0
: device allthough none is present. I have both an ed0 & an ep0 device
: in my config as I use both type of
It seems Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Michael
>Reifenberger writes:
> : if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
>
> The ep driver works in -current.
>
> : The message from pccardc is that he failed the resouce allocation.
>
> Fix the
In message <[EMAIL PROTECTED]> Michael
Reifenberger writes:
: if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
The ep driver works in -current.
: The message from pccardc is that he failed the resouce allocation.
Fix the resource allocation error. :-) That's reall
Michael Reifenberger wrote:
> Hi,
> if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
> The message from pccardc is that he failed the resouce allocation.
> A Kernel: "FreeBSD 4.0-CURRENT #0: Wed Jul 14 00:14:01 CEST 1999" works for e
p0
> but has the same error for
Hi,
if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
The message from pccardc is that he failed the resouce allocation.
A Kernel: "FreeBSD 4.0-CURRENT #0: Wed Jul 14 00:14:01 CEST 1999" works for ep0
but has the same error for sio*.
So under -current now at least ep* a
13 matches
Mail list logo
