IDE

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 --]

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

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

[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

[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

[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

[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, 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

[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

[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

[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: 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

[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

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...