I recently installed -current to ThinkPad X22. Though it seems that
X22's PC-Card slots work fine with -stable, in -current when probing
PCICs I got following message,
pcic0: mem 0x5000-0x5fff irq 11 at device
3.0 on pci2
pcib2: device pcic0 requested unsupported memory range 0x5000
From: Takanori Watanabe <[EMAIL PROTECTED]>
Date: Wed, 06 Feb 2002 23:16:21 +0900
> >I recently installed -current to ThinkPad X22. Though it seems that
> >X22's PC-Card slots work fine with -stable, in -current when probing
> >PCICs I got following message,
:
> How about disabling ACPI? I
From: "M. Warner Losh" <[EMAIL PROTECTED]>
Date: Wed, 06 Feb 2002 19:33:32 -0700 (MST)
> Hmmm. This looks ugly. :-( I can't boot with acpi enabled on my Dell
> Inspiron 8000. I can boot with apm enabled. There are issues with
> routing interrupts accross PCI PCI bridges at the moment when the
Next_Part(Wed_Feb__6_23:02:07_2002_731)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I recently installed -current to ThinkPad X22. Though it seems that
X22's PC-Card slots work fine with -stable, in -current when probing
PCICs I got following message,
pcic0:
Sorry for late reply. I didn't have time to test it.
From: "M. Warner Losh" <[EMAIL PROTECTED]>
Date: Thu, 07 Feb 2002 10:04:35 -0700 (MST)
> Yes. This is the ISA problem. The checks are there to make sure we
> don't assign addresses that aren't decoded by the bridge. However,
> the bridge doe
://home.jp.freebsd.org/~non/scsi_low-2926.tar.gz (added files)
http://home.jp.freebsd.org/~non/scsi_low-2926.diff.gz (diff to current)
http://home.jp.freebsd.org/~non/scsi_low4-2926.diff.gz (diff to stable)
You will need the tar.gz file and one of diff.gz file.
// Noriaki Mitsunaga
To
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Wed, 27 Sep 2000 15:01:13 +0200
> >I would like to have review especially on the changes in
> >i386/isa/clock.c for counting delay loop numbers,
>
> Could you explain the functionality you need here ? We already
> have a DELAY() macro/function i
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Wed, 27 Sep 2000 15:13:27 +0200
> >And we initialize the delaycount in clock.c.
>
> This is called "busy polling" and there must be a better way to do it.
Do you have any suggestions ?
> Has this code been profiled to examine typical actual dela
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
Date: Wed, 27 Sep 2000 15:25:42 +0200
> Use a normal timeout ?
I changed to use timeout() and now they do not change clock.c.
Updated files can be obtained from,
http://home.jp.freebsd.org/~non/scsi_low-2930.tar.gz (added fi
I changed to use timeout() and now they do not change clock.c.
>
> Updated files can be obtained from,
> http://home.jp.freebsd.org/~non/scsi_low-2930.tar.gz (added files)
> http://home.jp.freebsd.org/~non/scsi_low-2930.diff.gz (diff to current)
> http://home.jp.freebsd.org/~n
From: "David O'Brien" <[EMAIL PROTECTED]>
Date: Tue, 24 Oct 2000 13:15:26 -0700
> Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers.
Please do not remove them. Many people are waiting for them to switch
from 3.x with PAO3 or even with 2.x with PAO to more recent FreeBSD.
/
From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
Date: Mon, 5 Feb 2001 17:00:41 -0700
> I think we already have the most important functionality from the od(4)
> driver in the da and cd drivers. If there are any features that are
> in the od(4) driver that should be in the da(4) or cd(4) drivers, but
From: Bernd Walter <[EMAIL PROTECTED]>
Date: Tue, 6 Feb 2001 13:30:30 +0100
> > Though I have not tried `da' lately, if you don't insert a medium in
> > the drive at the time of CAM rescan bus, `da' tries to get the
> > geometry by XPT_CALC_GEOMETRY then panics with divided by zero in most
> > SCS
From: Bernd Walter <[EMAIL PROTECTED]>
Date: Wed, 7 Feb 2001 17:11:57 +0100
> On Tue, Feb 06, 2001 at 11:21:12PM +0900, [EMAIL PROTECTED] wrote:
> > Today I tried with 4.2-RELEASE (sorry not -current) and,
> > 1. Boot up the 4.2-RELEASE with GENERIC kernel.
> > 2. Connect MO drive with PC Card SCS
From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
Subject: Re: od driver for -CURRENT
> > By the way, in Japanese users mailing list, some said that `da' does
> > not check whether a medium is writerable or not (write
> > protected). If you mount a write protected medium with -rw, it will
> > lead bad
From: Bruce Evans <[EMAIL PROTECTED]>
Date: Sat, 10 Feb 2001 06:24:20 +1100 (EST)
> On Fri, 9 Feb 2001 [EMAIL PROTECTED] wrote:
> > From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
> > > Hmm, can you demonstrate the problem? The write-protect check in the od
> > > driver is one of the things that the
they are write protected on the first
> > write, etc. For the devices where we can tell, we should make the check
> > in open, but not rely on that catching all cases where a driver will
> > return EACCESS.
>
> Also, writing to a write protected sector is a special ca
From: Warner Losh <[EMAIL PROTECTED]>
Date: Fri, 31 May 2002 17:39:55 -0600
> In message <[EMAIL PROTECTED]> Alfred Perlstein writes:
> : I'm really fine with either. Let's wait till tomorrow for anyone to
> : speak up, if no one does please feel free to commit whichever one you
> : feel more com
18 matches
Mail list logo
