In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: Now I'm looking forward to the newcard cardbus support so I can finally use
: the 575BT which came with the laptop. (Tapping fingers impatiently. :-)
Hope you are tapping something soft :-) Wouldn't want you to hurt
yourself, or have others
In message <[EMAIL PROTECTED]> Will Andrews writes:
: On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
: > Interestingly, I rebuilt world with the latest pccardd changes and,
: > suddenly, the 589D started working perfectly. Unfortunately, the
: > 574BT doesn't work at all now. It a
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Will Andrews writes:
> : On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
> : > Interestingly, I rebuilt world with the latest pccardd changes and,
> : > suddenly, the 589D started working perfectly. Unfortunately, the
> : > 574BT d
On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote:
> Interestingly, I rebuilt world with the latest pccardd changes and,
> suddenly, the 589D started working perfectly. Unfortunately, the
> 574BT doesn't work at all now. It appears to configure properly, but
> it doesn't transmit or r
On Tue, 18 Jan 2000, Frank Mayhar wrote:
> Interestingly, I rebuilt world with the latest pccardd changes and,
> suddenly, the 589D started working perfectly. Unfortunately, the
> 574BT doesn't work at all now. It appears to configure properly, but
> it doesn't transmit or receive.
Ok, I need t
Greg Lehey wrote:
> The fact it's appearing with two different cards which work for other
> people tends to point away from the cards and towards some common
> factor, such as your laptop.
True.
Interestingly, I rebuilt world with the latest pccardd changes and,
suddenly, the 589D started workin
On Monday, 17 January 2000 at 8:24:20 -0800, Frank Mayhar wrote:
> Sorry for the delay on this reply; I was going over some old email and
> came across this only a week late.
>
> Jonathan Chen wrote:
>> With what little pccard/ethernet programming experiences I've had, this
>> problem seems to be
Sorry for the delay on this reply; I was going over some old email and
came across this only a week late.
Jonathan Chen wrote:
> With what little pccard/ethernet programming experiences I've had, this
> problem seems to be caused by the interrupt for the card getting lost
> somewhere before getti
On Mon, 10 Jan 2000, Warner Losh wrote:
> I don't think this is the problem. The pccard interface has one
> interrupt pin that is mapped by the pcic bridge (or some other
> pccard/cardbus bridge) to the main bus of the system. I didn't change
> that from the 3.x driver...
Indeed. The watchdog
In message <[EMAIL PROTECTED]> Jonathan Chen writes:
: "Fake IRQ must be 3". Now maybe the card requires it, or maybe the
: original author just didn't have anything on IRQ 3, I don't know. So, I'd
: suggest turning off com2 or whatever you have on irq3, -or- change the
: "fake irq" to something
On Sun, Jan 09, 2000 at 09:26:45PM -0700, Warner Losh wrote:
> [[ Moved to just current ]]
>
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : That may be the answer for Darren's problem. It's definitely not the
> : case for the ones we have been discussing on -mobile.
>
> There are defin
[[ Moved to just current ]]
In message <[EMAIL PROTECTED]> Greg Lehey writes:
: That may be the answer for Darren's problem. It's definitely not the
: case for the ones we have been discussing on -mobile.
There are definitely known issues with the ep0 driver. Right now it
doesn't interrupt qui
On Friday, 7 January 2000 at 23:46:49 +1100, Darren Reed wrote:
> In some email I received from Warner Losh, sie wrote:
>>
>> In message <[EMAIL PROTECTED]> Josef Karthauser writes:
>> : My 3c589d works just fine now, along with suspend/resume :) (under 4.0).
>>
>> The issue with the 3c589d is w
13 matches
Mail list logo
