IDE

IDE

[Barbier, Renaud (GE Infrastructure)]

I have a custom 440GX board with a Promise 20269.
even though, I used the options ide3=3Dnoprobe or hdg=3Dnoprobe and =
hdh=3Dnoprobe
Linux hangs on probing the second interface.=20
Am using the kernel options the correct way?

Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with =
idebus=3Dxx
PDC20269: IDE controller at PCI slot 00:03.0
PDC20269: chipset revision 2
PDC20269: not 100% native mode: will probe irqs later
PDC20269: ROM enabled at 0x000dc000
    ide2: BM-DMA at 0xefd0-0xefd7, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xefd8-0xefdf, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: STI Flash 6.2.0, CFA DISK drive
blk: queue c01dbea0, I/O limit 4095Mb (mask 0xffffffff)
Probing IDE interface ide3...

Re: IDE

[Sergei Shtylyov]

Hello.

Sébastien Chrétien wrote:

> I saw pata_of_platform source. And when is called pata_of_platform_probe ?

   Look at the very end of arch/powerpc/boot/dts/mpc8349emitx.dts; 
probably there are more examples in that directory...

MBR, Sergei

Re: IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

I saw pata_of_platform source. And when is called pata_of_platform_probe ?

2008/9/11, Sébastien Chrétien <sebastien.chretien.enseirb@gmail.com>:
>
> Where can I find a pata_of_platform node example ?
>
> Sergei Shtylyov a écrit :
>
>> Arnd Bergmann wrote:
>>
>>   Most probably you can use the existing platform drivers:
>>>> drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
>>>> Create/register a platform device named "pata_platform" with 2 memory
>>>> and 1 IRQ resource, and enable one of those drivers.
>>>>
>>>
>>  For new boards using a flattened device tree, it should be enough
>>> to add a device node for the pata_of_platform driver.
>>>
>>
>>   Oops, forgot about this one. No wonder, after being knee deep in ARM for
>> several months. :-)
>>
>> MBR, Sergei
>>
>>

[-- Attachment #2: Type: text/html, Size: 1725 bytes --]

Re: IDE

[Sébastien Chrétien]

Where can I find a pata_of_platform node example ?

Sergei Shtylyov a écrit :
> Arnd Bergmann wrote:
>
>>>   Most probably you can use the existing platform drivers: 
>>> drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
>>> Create/register a platform device named "pata_platform" with 2 
>>> memory and 1 IRQ resource, and enable one of those drivers.
>
>> For new boards using a flattened device tree, it should be enough
>> to add a device node for the pata_of_platform driver.
>
>    Oops, forgot about this one. No wonder, after being knee deep in 
> ARM for several months. :-)
>
> MBR, Sergei
>

Re: IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

ok I will use the flat device tree.
Do you utils in order to use ata and check ata link ?
For example, to read some information of my compact flash

2008/9/10, Sergei Shtylyov <sshtylyov@ru.mvista.com>:
>
> Arnd Bergmann wrote:
>
>   Most probably you can use the existing platform drivers:
>>> drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
>>> Create/register a platform device named "pata_platform" with 2 memory and
>>> 1 IRQ resource, and enable one of those drivers.
>>>
>>
>  For new boards using a flattened device tree, it should be enough
>> to add a device node for the pata_of_platform driver.
>>
>
>   Oops, forgot about this one. No wonder, after being knee deep in ARM for
> several months. :-)
>
> MBR, Sergei
>

[-- Attachment #2: Type: text/html, Size: 1478 bytes --]

Re: IDE

[Sergei Shtylyov]

Arnd Bergmann wrote:

>>   Most probably you can use the existing platform drivers: 
>>drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
>>Create/register a platform device named "pata_platform" with 2 memory 
>>and 1 IRQ resource, and enable one of those drivers.

> For new boards using a flattened device tree, it should be enough
> to add a device node for the pata_of_platform driver.

    Oops, forgot about this one. No wonder, after being knee deep in ARM for 
several months. :-)

MBR, Sergei

Re: IDE

[Arnd Bergmann]

On Wednesday 10 September 2008, S=E9bastien Chr=E9tien wrote:
> I looked falconide.c, it uses     hw_regs_t hw; and ide_hwif_t *hwif.
> Is it a good way ?
>=20

No, that uses the legacy IDE drivers, not the current ATA drivers,
and it is not based on the device tree information.

Just use drivers/ata/pata_of_platform.c, you probably don't even
need to change the code, just your device tree.

	Arnd <><

Re: IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

I looked falconide.c, it uses     hw_regs_t hw; and ide_hwif_t *hwif.
Is it a good way ?

2008/9/10, Arnd Bergmann <arnd@arndb.de>:
>
> On Wednesday 10 September 2008, Sergei Shtylyov wrote:
> >    Most probably you can use the existing platform drivers:
> > drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
> > Create/register a platform device named "pata_platform" with 2 memory
> > and 1 IRQ resource, and enable one of those drivers.
>
>
> For new boards using a flattened device tree, it should be enough
> to add a device node for the pata_of_platform driver.
> If you need a device specific setup, you should add a new "compatible"
> value in the tree and make the driver handle that in whatever
> way you need.
>
>
>         Arnd <><
>

[-- Attachment #2: Type: text/html, Size: 1149 bytes --]

Re: IDE

[Arnd Bergmann]

On Wednesday 10 September 2008, Sergei Shtylyov wrote:
> =A0 =A0Most probably you can use the existing platform drivers:=20
> drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
> Create/register a platform device named "pata_platform" with 2 memory=20
> and 1 IRQ resource, and enable one of those drivers.

=46or new boards using a flattened device tree, it should be enough
to add a device node for the pata_of_platform driver.
If you need a device specific setup, you should add a new "compatible"
value in the tree and make the driver handle that in whatever
way you need.

	Arnd <><

Re: IDE

[Sergei Shtylyov]

Hello.

Sébastien Chrétien wrote:

> Have I to rewrite a IDE driver ?

   Most probably you can use the existing platform drivers: 
drivers/ide/egacy/ide_platform.c or drivers/ata/pata_platform.c.
Create/register a platform device named "pata_platform" with 2 memory 
and 1 IRQ resource, and enable one of those drivers.

> 2008/9/10, Sergei Shtylyov <sshtylyov@ru.mvista.com 
> <mailto:sshtylyov@ru.mvista.com>>:
>
>     Hello.
>
>     Sébastien Chrétien wrote:
>
>         I would like to setup my IDE controller. It uses a generic
>         mapping. And he is located at the adress 0x20003000.
>
>
>      What kin of controller, and what do you mean by generic mapping?
>
>         How can I specifie this adress to the ide driver ?
>
>
>      The usual ways is via the platform device.
>
>

MBR, Sergei

Re: IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

It is a common ide controller :
offset 0x0 Data
offset 0x1 error
offset 0x2 Sector count
offset 0x3 sector No
offset 0x4 Cylinder low
offset 0x5 Cylinder High
offset 0x6 Head
offset 0x7 status

2008/9/10, Sergei Shtylyov <sshtylyov@ru.mvista.com>:
>
> Hello.
>
> Sébastien Chrétien wrote:
>
>  I would like to setup my IDE controller. It uses a generic mapping. And he
>> is located at the adress 0x20003000.
>>
>
>  What kin of controller, and what do you mean by generic mapping?
>
>  How can I specifie this adress to the ide driver ?
>>
>
>  The usual ways is via the platform device.
>
>
> MBR, Sergei
>
>
>

[-- Attachment #2: Type: text/html, Size: 1295 bytes --]

Re: IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

Have I to rewrite a IDE driver ?

2008/9/10, Sergei Shtylyov <sshtylyov@ru.mvista.com>:
>
> Hello.
>
> Sébastien Chrétien wrote:
>
>  I would like to setup my IDE controller. It uses a generic mapping. And he
>> is located at the adress 0x20003000.
>>
>
>  What kin of controller, and what do you mean by generic mapping?
>
>  How can I specifie this adress to the ide driver ?
>>
>
>  The usual ways is via the platform device.
>
>
> MBR, Sergei
>
>
>

[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

Re: IDE

[Sergei Shtylyov]

Hello.

Sébastien Chrétien wrote:

> I would like to setup my IDE controller. It uses a generic mapping. 
> And he is located at the adress 0x20003000.

   What kin of controller, and what do you mean by generic mapping?

> How can I specifie this adress to the ide driver ?

   The usual ways is via the platform device.


MBR, Sergei

IDE

[Sébastien Chrétien]

[-- Attachment #1: Type: text/plain, Size: 170 bytes --]

Hello

I would like to setup my IDE controller. It uses a generic mapping. And he
is located at the adress 0x20003000.
How can I specifie this adress to the ide driver ?

[-- Attachment #2: Type: text/html, Size: 186 bytes --]

IDE

[Ian Molton]

Hi.

I've got an old IDE disc (Quantum Maverick 270A) and it appears to be
detected OK, however I get about 15 hda: lost interrupt between
detection and printing the partition table (which seems to go OK).

this is on 2.5.69, with my own IDE driver (which I ported from 2.4.16)

any ideas? I heard 2.5 doesnt like some very old drives...

-- 
Spyros lair: http://www.mnementh.co.uk/
Do not meddle in the affairs of Dragons, for you are tasty and good with
ketchup.

Systems programmers keep it up longer.

IDE

[Anders Widman]

As there seem to be more activity now, maybe someone can help me get
UDMA 66/100 to work with Promise U100 cards.

I have tested on three different systems with 4 brands (Maxtor,
Seagate, Quantum, IBM) of harddrives. The highest mode I can set is
UDMA33. When I try to use anything higher I get an error in the kernel
log saying "kernel: ide2: Speed warnings UDMA 3/4/5 is not functional".

All drives support higher at least UDMA 100.

I have tested with most of the 2.4.17-19 kernels, including the Red
Hat kernels under Red Hat 7.2 and 7.3. I have also used the -AC
patches.  I have also compiled with and without "IGNORE word93
Validation BITS"

The current kernel is 2.4.19-rc1.


dmesg log says this om my current system:
---

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:DMA
PDC20268: IDE controller on PCI bus 00 dev 48
PCI: Found IRQ 4 for device 00:09.0
PCI: Sharing IRQ 4 with 00:04.2
PDC20268: chipset revision 2
PDC20268: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0x9800-0x9807, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x9808-0x980f, BIOS settings: hdg:pio, hdh:pio
PDC20268: IDE controller on PCI bus 00 dev 58
PCI: Found IRQ 10 for device 00:0b.0 
PDC20268: chipset revision 2
PDC20268: not 100% native mode: will probe irqs later
    ide4: BM-DMA at 0x8000-0x8007, BIOS settings: hdi:pio, hdj:pio
    ide5: BM-DMA at 0x8008-0x800f, BIOS settings: hdk:pio, hdl:pio

---
hde: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(33)
hdf: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63, UDMA(33)
hdg: 320173056 sectors (163929 MB) w/2048KiB Cache, CHS=19929/255/63, UDMA(33)
hdh: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=14946/255/63, UDMA(33)
hdi: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(33)
hdj: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=158816/16/63, UDMA(33)
hdk: 117266688 sectors (60041 MB) w/2000KiB Cache, CHS=116336/16/63, UDMA(33)
hdl: 117266688 sectors (60041 MB) w/2000KiB Cache, CHS=116336/16/63, UDMA(33)
---
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xb000-0xb007,0xa802 on irq 4
ide3 at 0xa400-0xa407,0xa002 on irq 4
ide4 at 0x9400-0x9407,0x9002 on irq 10
ide5 at 0x8800-0x8807,0x8402 on irq 10
---
hde: ST360021A, ATA DISK drive
hdf: IC35L060AVER07-0, ATA DISK drive
hdg: Maxtor 4G160J8, ATA DISK drive
hdh: Maxtor 4G120J6, ATA DISK drive
hdi: Maxtor 98196H8, ATA DISK drive
hdj: Maxtor 98196H8, ATA DISK drive
hdk: MAXTOR 4K060H3, ATA DISK drive
hdl: MAXTOR 4K060H3, ATA DISK driv



The Promise U100Tx2 BIOS does report UDMA100 for ALL drives.

Re: IDE

[Alessandro Suardi]

Andries.Brouwer@cwi.nl wrote:
> < Recap >
> 
> == I have had problems with 2.5.10 (first few blocks of the root
> == filesystem overwritten) and then went back to 2.5.8 that I had
> == used for a while already, but then also noticed corruption there.
> == Back at 2.4.17 today..
> 
> < Optimistic reply >
> 
> = It could very well be that the recent changes could have cured this.
> 
> < Reality of today >
> 
> Booted a vanilla 2.5.12. It did not succeed in mounting the root
> filesystem, but instead wrote zeros over the superblock.
> 
> 	hdb: task_out_intr: error=0x04 { DriveStatusError }
> 
> Will try 2.5.13 later.

Managed to boot all versions (though some ext3 journal replay
  showed up even after clean shutdowns), seems to be okay and
  mashed my disk with installing of Portal today - no issue,
  only a positive note for the 2.5.13 VM which allowed me to
  finish in 48' what 2.4.19-pre7 couldn't finish in over 2h.

Dell laptop with a PIIX4 chipset, btw.

--alessandro

  "the hands that build / can also pull down
    even the hands of love"
                             (U2, "Exit")

IDE

[Andries.Brouwer]

< Recap >

== I have had problems with 2.5.10 (first few blocks of the root
== filesystem overwritten) and then went back to 2.5.8 that I had
== used for a while already, but then also noticed corruption there.
== Back at 2.4.17 today..

< Optimistic reply >

= It could very well be that the recent changes could have cured this.

< Reality of today >

Booted a vanilla 2.5.12. It did not succeed in mounting the root
filesystem, but instead wrote zeros over the superblock.

	hdb: task_out_intr: error=0x04 { DriveStatusError }

Will try 2.5.13 later.

Andries


[So, 2.5.8 causes very slow corruption, and can be used for
several hours, sometimes days, before something bad happens.
And bad things only happen to disks on HPT366.
On the other hand, 2.5.10 and 2.5.12 fail directly at boot
in precisely the same way and with a disk on the mb.]

% grep _IDE .config | grep -v '#'
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y