On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
> On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
>
> > append "hdd=ide-scsi"
>
> append "hdd=scsi" is better.
Care to explain why?
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O|
On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
append "hdd=ide-scsi"
append "hdd=scsi" is better.
Care to explain why?
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O|
Oct 7 18:48:01 manos PAM_pwdb[727]: (login) session opened for user root by
LOGIN(uid=0)
Oct 7 18:48:08 manos kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI
devices
Oct 7 18:48:08 manos kernel: scsi : 2 hosts.
Oct 7 18:49:32 manos PAM_pwdb[728]: (login) session opened for user
On Fri, 6 Oct 2000, Andre Hedrick wrote:
> void go_take_a_dump (float load)
> {
> if (pull_down_pants() && purge_bowles() && wipe_anus() && pull_up_pants())
> flush(load);
> else
> wear(load);
> }
But here you make another classic mistake. Consider the case where
purge_bowels()
On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
> On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
>
> > append "hdd=ide-scsi"
Am I doing this wrong? It seems to work.
:-)
Jeff
>
> append "hdd=scsi" is better.
>
> Andre Hedrick
> The Linux ATA/IDE guy
>
-
To unsubscribe from
On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
> append "hdd=ide-scsi"
append "hdd=scsi" is better.
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
On Sat, Oct 07, 2000 at 10:03:34AM +0200, Jens Axboe wrote:
> On Sat, Oct 07 2000, Dax Kelson wrote:
> > > BTW, how did your testing of the speed=4 problem with ide-scsi turn
> > > out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
> > > get the drive to burn clean unless the
> Something like this?
Close but now there is no select.
--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c Sat Sep 23
01:04:46 2000
+++ drivers/scsi/ide-scsi.c Sat Oct 7 10:52:13 2000
@@ -435,7 +435,6 @@
+ SELECT_DRIVE(HWIF(drive), drive);
if (IDE_CONTROL_REG)
On Sat, Oct 07 2000, Andre Hedrick wrote:
> > I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
> > problems (this is on two different atapi writers). This could be an
> > ide-scsi bug on some models. The folks who are seeing corruption, could
> > they try and narrow it down?
On Sat, 7 Oct 2000, Jens Axboe wrote:
> I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
> problems (this is on two different atapi writers). This could be an
> ide-scsi bug on some models. The folks who are seeing corruption, could
> they try and narrow it down? Is it
On Sat, Oct 07 2000, Dax Kelson wrote:
> > BTW, how did your testing of the speed=4 problem with ide-scsi turn
> > out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
> > get the drive to burn clean unless the speed setting is cranked down to
> > speed=2.
> >
> > Jeff
>
> I
Jeff V. Merkey said once upon a time (Fri, 6 Oct 2000):
>
> Andre,
>
> BTW, how did your testing of the speed=4 problem with ide-scsi turn
> out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
> get the drive to burn clean unless the speed setting is cranked down to
>
Jeff V. Merkey said once upon a time (Fri, 6 Oct 2000):
Andre,
BTW, how did your testing of the speed=4 problem with ide-scsi turn
out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
get the drive to burn clean unless the speed setting is cranked down to
speed=2.
On Sat, Oct 07 2000, Dax Kelson wrote:
BTW, how did your testing of the speed=4 problem with ide-scsi turn
out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
get the drive to burn clean unless the speed setting is cranked down to
speed=2.
Jeff
I just burned
On Sat, 7 Oct 2000, Jens Axboe wrote:
I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
problems (this is on two different atapi writers). This could be an
ide-scsi bug on some models. The folks who are seeing corruption, could
they try and narrow it down? Is it random
On Sat, Oct 07 2000, Andre Hedrick wrote:
I regurlarly burn CD-R with ide-scsi on 2.4, and I've not noticed any
problems (this is on two different atapi writers). This could be an
ide-scsi bug on some models. The folks who are seeing corruption, could
they try and narrow it down? Is it
Something like this?
Close but now there is no select.
--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c Sat Sep 23
01:04:46 2000
+++ drivers/scsi/ide-scsi.c Sat Oct 7 10:52:13 2000
@@ -435,7 +435,6 @@
+ SELECT_DRIVE(HWIF(drive), drive);
if (IDE_CONTROL_REG)
On Sat, Oct 07, 2000 at 10:03:34AM +0200, Jens Axboe wrote:
On Sat, Oct 07 2000, Dax Kelson wrote:
BTW, how did your testing of the speed=4 problem with ide-scsi turn
out. We are still seeing the speed=2 problem on 2.4.0-pre9. I cannot
get the drive to burn clean unless the speed
On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
append "hdd=ide-scsi"
append "hdd=scsi" is better.
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
append "hdd=ide-scsi"
Am I doing this wrong? It seems to work.
:-)
Jeff
append "hdd=scsi" is better.
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list:
On Fri, 6 Oct 2000, Andre Hedrick wrote:
void go_take_a_dump (float load)
{
if (pull_down_pants() purge_bowles() wipe_anus() pull_up_pants())
flush(load);
else
wear(load);
}
But here you make another classic mistake. Consider the case where
purge_bowels() fails
Oct 7 18:48:01 manos PAM_pwdb[727]: (login) session opened for user root by
LOGIN(uid=0)
Oct 7 18:48:08 manos kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI
devices
Oct 7 18:48:08 manos kernel: scsi : 2 hosts.
Oct 7 18:49:32 manos PAM_pwdb[728]: (login) session opened for user
Andre,
(Thanks for calling my bluff) && (I was wrong).
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Sean Estabrooks wrote:
>
> Hi Andre,
>
> The if() logic must then rely on implementation specific compiler
> details and not have any optimizations which break this code. While it may
> "WORK" it isn't particularly reliable code.
>
> Sean
Nope, the logical ops are sequence
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
> Hi Andre,
>
> The if() logic must then rely on implementation specific compiler
> details and not have any optimizations which break this code. While it may
> "WORK" it isn't particularly reliable code.
If that is the case and it is proven
Hi Andre,
The if() logic must then rely on implementation specific compiler
details and not have any optimizations which break this code. While it may
"WORK" it isn't particularly reliable code.
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
, Sean Estabrooks wrote:
>
> > ide-pci.c bug:
> >
> > ide_setup_pci_baseregs() may inappropriately report device as not capable of full
>native PCI:
> >
> > // BUGGY LINE:
> > if (pci_read_config_byte(dev, PCI_CLASS_PROG, ) || (progif & 5) !=
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
> ide-pci.c bug:
>
> ide_setup_pci_baseregs() may inappropriately report device as not capable of full
>native PCI:
>
> // BUGGY LINE:
> if (pci_read_config_byte(dev, PCI_CLASS_PROG, ) || (progif & 5) != 5
ide-pci.c bug:
ide_setup_pci_baseregs() may inappropriately
report device as not capable of full native PCI:
// BUGGY LINE:
if (pci_read_config_byte(dev,
PCI_CLASS_PROG, ) || (progif & 5) != 5)
{// = TWO CONDITIONS USING PROGIF
if ((progif &a
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
ide-pci.c bug:
ide_setup_pci_baseregs() may inappropriately report device as not capable of full
native PCI:
// BUGGY LINE:
if (pci_read_config_byte(dev, PCI_CLASS_PROG, progif) || (progif 5) != 5) {
// = TWO
wrote:
ide-pci.c bug:
ide_setup_pci_baseregs() may inappropriately report device as not capable of full
native PCI:
// BUGGY LINE:
if (pci_read_config_byte(dev, PCI_CLASS_PROG, progif) || (progif 5) != 5) {
// = TWO CONDITIONS USING PROGIF
Hi Andre,
The if() logic must then rely on implementation specific compiler
details and not have any optimizations which break this code. While it may
"WORK" it isn't particularly reliable code.
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Fri, 6 Oct 2000, Sean Estabrooks wrote:
Hi Andre,
The if() logic must then rely on implementation specific compiler
details and not have any optimizations which break this code. While it may
"WORK" it isn't particularly reliable code.
If that is the case and it is proven then
Sean Estabrooks wrote:
Hi Andre,
The if() logic must then rely on implementation specific compiler
details and not have any optimizations which break this code. While it may
"WORK" it isn't particularly reliable code.
Sean
Nope, the logical ops are sequence points
Andre,
(Thanks for calling my bluff) (I was wrong).
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
35 matches
Mail list logo
