From: "Rogério Brito" <rbrito@ime.usp.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Tue, 28 Dec 2004 00:44:48 -0200 [thread overview]
Message-ID: <20041228024447.GB13559@ime.usp.br> (raw)
In-Reply-To: <1104194716.20898.60.camel@localhost.localdomain>
On Dec 28 2004, Alan Cox wrote:
> Correct - IDE lacks "disconnect" so when the bus is locked during
> something like a CD verify during a burn you don't get access to the
> other device.
Yes, that was the problem that I was trying to circumvent.
> > > As it was a nuisance, I decided to put the CD-Writer on the Promise
> > > controller, which is an UDMA100 controller and, thus, I thought
> > > things would only get better.
> >
> > I remember reading somewhere that one should not connect ATAPI devices
> > to the Promise controller.
>
> Again exactly right - some promise controllers don't support ATAPI DMA.
Is there any way to circumvent the limitations via software? I have already
upgraded the firmware of my motherboard (and, if I understood it correctly,
it also upgraded the firmware of the Promise controller).
The funny thing is that right after the Power On Self Test, the devices are
probed and then the Promise controller says that the drive supports UDMA2.
Then, when Linux boots, I see this:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PDC20265: IDE controller at PCI slot 0000:00:11.0
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI interrupt 0000:00:11.0[A] -> GSI 10 (level, low) -> IRQ 10
PDC20265: chipset revision 2
PDC20265: 100%% native mode on irq 10
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:pio, hdh:pio
hdf: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> As a general rule:
> Put disks on the host first so they avoid the PCI bus overhead and
> dont fill it
> Put CD burners on host if you can
> Use external controllers for slower stuff
Ok, so if this is indeed buggy hardware, one way to make the system not
slow to a crawl would be to have:
* on ide0 the first HD and the DVD reader;
* on ide1 the second HD and the CD-Writer.
Since both ide0 and ide1 are VIA controllers, they would be able to cope
with DMA. It will be really a deception with this motherboard if I can't
use the Promise controller (which claimed to be ATA/100 when I bought it
and paid a good deal of money). :-(
Thanks for all your feedback and suggestions, Rogério Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
next prev parent reply other threads:[~2004-12-28 2:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 23:31 Linux 2.6.10-ac1 Alan Cox
2004-12-27 0:57 ` Bartlomiej Zolnierkiewicz
2004-12-27 1:25 ` Andreas Steinmetz
2004-12-27 1:40 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:28 ` Alan Cox
2004-12-27 15:46 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:45 ` Ross Biro
2004-12-27 15:38 ` Bartlomiej Zolnierkiewicz
2004-12-27 15:49 ` Andreas Steinmetz
2004-12-27 15:54 ` Bartlomiej Zolnierkiewicz
2004-12-27 16:02 ` Andreas Steinmetz
2004-12-27 16:54 ` Alan Cox
2004-12-27 14:36 ` Rafael J. Wysocki
2004-12-27 14:57 ` Andreas Steinmetz
2004-12-27 14:33 ` Alan Cox
2004-12-27 20:31 ` Rogério Brito
2004-12-27 20:43 ` Michal Schmidt
2004-12-28 0:45 ` Alan Cox
2004-12-28 2:44 ` Rogério Brito [this message]
2004-12-30 4:41 ` Gene Heskett
2004-12-30 5:05 ` Gene Heskett
2004-12-30 23:38 ` Alan Cox
2004-12-31 1:06 ` Gene Heskett
2004-12-31 9:57 ` Jan Dittmer
2004-12-31 12:05 ` Gene Heskett
2004-12-31 12:38 ` Jan Dittmer
2004-12-31 13:18 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041228024447.GB13559@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xschmi00@stud.feec.vutbr.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox