Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Terry Lambert writes:
> : Warner Losh wrote:
> : > : The problem with this is drivers that can't share
> : > : interrupts because there is no way to ask the hardware
> : > : which of several devices caused the interrupt. This
> : > : means that
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: Warner Losh wrote:
: > : The problem with this is drivers that can't share
: > : interrupts because there is no way to ask the hardware
: > : which of several devices caused the interrupt. This
: > : means that it's an attribute of the driver
Warner Losh wrote:
> : The problem with this is drivers that can't share
> : interrupts because there is no way to ask the hardware
> : which of several devices caused the interrupt. This
> : means that it's an attribute of the driver, not the
> : bus, so having the bus do this automatically woul
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: clk0 on i386 :-).
Ah, but that's extra special and not a real FreeBSD device :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 9 Jul 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Terry Lambert writes:
> : The problem with this is drivers that can't share
> : interrupts because there is no way to ask the hardware
> : which of several devices caused the interrupt. This
> : means that it's an attribute
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: Warner Losh wrote:
: > That is, I advocate all busses that support sharing to or in
: > RF_SHAREABLE when appropriate. The trouble is that with the current
: > interfaces, that precludes one from using fast interrupts. FAST or
: > not fast i
Warner Losh wrote:
> That is, I advocate all busses that support sharing to or in
> RF_SHAREABLE when appropriate. The trouble is that with the current
> interfaces, that precludes one from using fast interrupts. FAST or
> not fast is a property of bus_setup_intr, not bus_alloc_resource. sio
>
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > Actually, there is a reason. Ata is special like pcic is special.
: > Both of them can have multiple interrupt routing methods. When ata is
: > connected directly to the south bridge, it can route ISA interrupts,
: > even though it is a pci d
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: The upshot of this is that drivers should be setting RF_SHAREABLE if they
: themselves can handle the possibility that the motherboard is wired up for
: sharing their IRQ. It is up to the bus controller to sort out what is
: really electrically
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: The upshot of this is that drivers should be setting RF_SHAREABLE if they
: themselves can handle the possibility that the motherboard is wired up for
: sharing their IRQ. It is up to the bus controller to sort out what is
: really electrically
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : >
> : > sos> Well, sortof, the ata driver doesn't allow for sharing irq14&15
> : > sos> since lots of boards doesn't work that way. However if you need
> : > sos> it you can try to add the shared flag in the driver and se
> : There is absolutely no reason for the ata driver not to simply set
> : RF_SHAREABLE and be done with it. It's up to the driver's parent (isa,
> : pci, etc) to decide whether the interrupt is in fact shareable or not.
> :
> : The ata driver itself can share interrupts just fine, and it shou
In message <[EMAIL PROTECTED]> Mike Smith writes:
: >
: > sos> Well, sortof, the ata driver doesn't allow for sharing irq14&15
: > sos> since lots of boards doesn't work that way. However if you need
: > sos> it you can try to add the shared flag in the driver and see if
: > sos> it works on yo
>
> sos> Well, sortof, the ata driver doesn't allow for sharing irq14&15
> sos> since lots of boards doesn't work that way. However if you need
> sos> it you can try to add the shared flag in the driver and see if
> sos> it works on yours. Hmm, maybe I should make this tunable...
>
> It this p
sos> Well, sortof, the ata driver doesn't allow for sharing irq14&15
sos> since lots of boards doesn't work that way. However if you need
sos> it you can try to add the shared flag in the driver and see if
sos> it works on yours. Hmm, maybe I should make this tunable...
It this patch OK? I've
sos> Well, sortof, the ata driver doesn't allow for sharing irq14&15
sos> since lots of boards doesn't work that way. However if you need
sos> it you can try to add the shared flag in the driver and see if
sos> it works on yours.
I've changed src/sys/dev/ata/ata-pci.c with:
--- ata-pci.c.dist
It seems Makoto MATSUSHITA wrote:
>
> sos> Thats because of the runtime attach/detach code in current, if the
> sos> channel HW is there, its attached so you can add a device later
> sos> with atacontrol without having to boot. In -stable the channel is
> sos> not attached if no devices are pres
sos> Thats because of the runtime attach/detach code in current, if the
sos> channel HW is there, its attached so you can add a device later
sos> with atacontrol without having to boot. In -stable the channel is
sos> not attached if no devices are present at probe time.
Thanks for your clear ex
It seems Makoto MATSUSHITA wrote:
>
> % atacontrol info 0
> Master: ad0 ATA/ATAPI rev 5
> Slave: no device present
> % atacontrol info 1
> Master: no device present
> Slave: no device present
> % atacontrol info 2
> %
>
> Hmm, ata driver says there are two buses. But why? 4-st
mark> This looks right to me. One main PIIX4 ATA controller with two
mark> independent IDE channels (usually referred to as a Primary and a
mark> Secondary IDE controller). Usually the PC BIOS will allow you to
mark> turn on/off these channels independently. Does your bios allow
mark> you to turn
At 11:47 PM +0900 6/18/01, Makoto MATSUSHITA wrote:
>(from dmesg output)
>atapci0: port 0xf000-0xf00f at device
>7.1 on pci0
>ata0: at 0x1f0 irq 14 on atapci0
>ata1: at 0x170 irq 15 on atapci0
This looks right to me. One main PIIX4 ATA controller with two
independent IDE channels (usually refe
On Thu, 21 Jun 2001, Makoto MATSUSHITA wrote:
> matusita> I've just updated to 5-current as of yesterday (yeh!), but
> matusita> no helps. 'ata' driver detects the second devices which is
> matusita> _not_ on this machine.
>
> Since the kernel detects ata1 which eats IRQ 15, the kernel fail
> to
Forget to mention that:
matusita> I've just updated to 5-current as of yesterday (yeh!), but
matusita> no helps. 'ata' driver detects the second devices which is
matusita> _not_ on this machine.
Since the kernel detects ata1 which eats IRQ 15, the kernel fail to
attach the first fxp device (wh
matusita> I have similar problem; 'ata' bus is detected twice.
I've just updated to 5-current as of yesterday (yeh!), but no helps.
'ata' driver detects the second devices which is _not_ on this machine.
Attached below is a full and verbose dmesg output. Most part of
kernel configulation is as
jedgar> Commenting hints.psm.0.* and hint.atkbd.0.* from /boot/device.hints
jedgar> (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=84052+0+current/freebsd-current)
jedgar> works here.
I have similar problem; 'ata' bus is detected twice.
We jp.FreeBSD.org have donated TrustGuard iSV, which is 13
It seems Maxim Sobolev wrote:
> >
> > It seems Jim Bloom wrote:
> > > For the past couple weeks I have been unable to build a kernel for my
> > > laptop. I keep getting undefined symbols. The problem started with
> > > the split of the ata driver by different bus attachments. My laptop
> > > o
>
> It seems Jim Bloom wrote:
> > For the past couple weeks I have been unable to build a kernel for my
> > laptop. I keep getting undefined symbols. The problem started with
> > the split of the ata driver by different bus attachments. My laptop
> > only has ISA and not PCI so I don't include
It seems Jim Bloom wrote:
> For the past couple weeks I have been unable to build a kernel for my
> laptop. I keep getting undefined symbols. The problem started with
> the split of the ata driver by different bus attachments. My laptop
> only has ISA and not PCI so I don't include PCI in the k
For the past couple weeks I have been unable to build a kernel for my
laptop. I keep getting undefined symbols. The problem started with
the split of the ata driver by different bus attachments. My laptop
only has ISA and not PCI so I don't include PCI in the kernel config
file.
The errors and
Hi all,
Tried out the new ATAPI driver last night with a CVS from a couple of
days ago. All detected ok on boot but then I got a message roughly like:
timeout waiting for command
and then I get:
ata0: resetting devices ..
The system completely hung solid then.
Firstly a question. Is t
I've updated to the latest -current, and things have gone awry. At boot,
the console freezes
at the end of the dmesg. The startup process continues, tho, and I can
telnet into the box. Then madness ensues. The contents of some files I
create disappears, top freezes after listing the process
31 matches
Mail list logo
