Padraig,
Real short and simple, use hdX=flash for the slave.
I do not care about the argument anymore over what is ATA and what is CFA.
You read stuff and you believe. I know that everything is "STORAGE" is a
"BIG FAT LIE". Everytime I try to expose this fact people lose it.
So if you want
I'm still confused :-(
When you say:
"CFA is dropped into a pcmica/cardbus thingy.
Also there are no CFA's which are ATA devices by the definition, they
require a host-bridge to transport the signal. Handling host-bridges is
the problem. As more and stranger usages of these bridges happen the
I'm still confused :-(
When you say:
"CFA is dropped into a pcmica/cardbus thingy.
Also there are no CFA's which are ATA devices by the definition, they
require a host-bridge to transport the signal. Handling host-bridges is
the problem. As more and stranger usages of these bridges happen the
Padraig,
Real short and simple, use hdX=flash for the slave.
I do not care about the argument anymore over what is ATA and what is CFA.
You read stuff and you believe. I know that everything is "STORAGE" is a
"BIG FAT LIE". Everytime I try to expose this fact people lose it.
So if you want
hdx=flash is only a flag to deal with flash.
a better description is probe-slave-with-master-flash, or
to-hell-with-flash-go-look.
On Tue, 27 Mar 2001, Richard A. Smith wrote:
> On Tue, 27 Mar 2001 09:17:48 -0800 (PST), Andre Hedrick wrote:
>
> >not acceptable. If you have a complain take
On Tue, 27 Mar 2001 09:17:48 -0800 (PST), Andre Hedrick wrote:
>not acceptable. If you have a complain take it to CFA commitee and have
>them fix it.
Well my only real complaints are that 1) It was done silently.. 2) I could not
override it
w/o a code mod. Both of which are contrary to what
./linux/drivers/ide/ide.c
* "hdx=flash" : allows for more than one ata_flash disk to be
* registered. In most cases, only one device
* will be present.
On Tue, 27 Mar 2001, Padraig Brady wrote:
> How do you activate the
How do you activate the walk around you describe
to allow the detection of the slave? hda=ataflash?
Is this sort of stuff documented anywhere?
For those interested you also mention it here:
http://lists.sourceforge.net/archives//linux-usb-devel/2000-August/000929.html
This describes the other
Because 'real' ATA devices use a signature map the detects presense of
master slave during execute diagnostics. This is done in the BIOS.
CFA does no report this correctly and waiting for a 31 second time out is
not acceptable. If you have a complain take it to CFA commitee and have
them fix
OK the following assumes CF never have slaves which is just wrong.
The CF should be logically treated as an IDE harddisk. So the fix is
probably have a kernel parameter that causes the following check to
be skipped?
/*
* Prevent long system lockup probing later for non-existant
* slave
Because in laptops, the primary use of CFA.
Laptops using CFA do not have slaves.
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757
Can I just confirm that I'm seeing the same thing.
I'm using a pcengines compact flash adapter which has
a master/slave jumper, and this seems to confirm what
I thought, I.E. slaves are OK. Note I also had trouble where
HD was master and flashdisk was slave, where again the
CF was silently
Can I just confirm that I'm seeing the same thing.
I'm using a pcengines compact flash adapter which has
a master/slave jumper, and this seems to confirm what
I thought, I.E. slaves are OK. Note I also had trouble where
HD was master and flashdisk was slave, where again the
CF was silently
Because in laptops, the primary use of CFA.
Laptops using CFA do not have slaves.
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757
OK the following assumes CF never have slaves which is just wrong.
The CF should be logically treated as an IDE harddisk. So the fix is
probably have a kernel parameter that causes the following check to
be skipped?
/*
* Prevent long system lockup probing later for non-existant
* slave
Because 'real' ATA devices use a signature map the detects presense of
master slave during execute diagnostics. This is done in the BIOS.
CFA does no report this correctly and waiting for a 31 second time out is
not acceptable. If you have a complain take it to CFA commitee and have
them fix
How do you activate the walk around you describe
to allow the detection of the slave? hda=ataflash?
Is this sort of stuff documented anywhere?
For those interested you also mention it here:
http://lists.sourceforge.net/archives//linux-usb-devel/2000-August/000929.html
This describes the other
./linux/drivers/ide/ide.c
* "hdx=flash" : allows for more than one ata_flash disk to be
* registered. In most cases, only one device
* will be present.
On Tue, 27 Mar 2001, Padraig Brady wrote:
How do you activate the
On Tue, 27 Mar 2001 09:17:48 -0800 (PST), Andre Hedrick wrote:
not acceptable. If you have a complain take it to CFA commitee and have
them fix it.
Well my only real complaints are that 1) It was done silently.. 2) I could not
override it
w/o a code mod. Both of which are contrary to what I
hdx=flash is only a flag to deal with flash.
a better description is probe-slave-with-master-flash, or
to-hell-with-flash-go-look.
On Tue, 27 Mar 2001, Richard A. Smith wrote:
On Tue, 27 Mar 2001 09:17:48 -0800 (PST), Andre Hedrick wrote:
not acceptable. If you have a complain take it
I spent most of the day today trying to track down why the embedded system I am
working
on would not recognize hdb on boot. It refused to show in the devices list even
though I
specifically told the kernel it existed with the hdb=c,h,s option.
After working on what seemed like a hardware
I spent most of the day today trying to track down why the embedded system I am
working
on would not recognize hdb on boot. It refused to show in the devices list even
though I
specifically told the kernel it existed with the hdb=c,h,s option.
After working on what seemed like a hardware
22 matches
Mail list logo
