The hardware is called (E)IDE, the protocol is called ATA.
Or that's what I was told -- I think there's some historic
revisionism involved, too.
ATA is the interface and standards for the ANSI standards based disk
attachment. IDE "Integrated Drive Electronics" is a marketing name used
to cover
The hardware is called (E)IDE, the protocol is called ATA.
Or that's what I was told -- I think there's some historic
revisionism involved, too.
ATA is the interface and standards for the ANSI standards based disk
attachment. IDE Integrated Drive Electronics is a marketing name used
to cover
Hello.
Segher Boessenkool wrote:
+[EMAIL PROTECTED] {
+compatible = "mmio-ide";
+device_type = "ide";
Why not "ata"?
The hardware is called (E)IDE, the protocol is called ATA.
Sorry for not denouncing this earlier. :-)
ATA is the name of ANSI standard
Hello.
Segher Boessenkool wrote:
+[EMAIL PROTECTED] {
+compatible = mmio-ide;
+device_type = ide;
Why not ata?
The hardware is called (E)IDE, the protocol is called ATA.
Sorry for not denouncing this earlier. :-)
ATA is the name of ANSI standard describing
> The hardware is called (E)IDE, the protocol is called ATA.
> Or that's what I was told -- I think there's some historic
> revisionism involved, too.
ATA is the interface and standards for the ANSI standards based disk
attachment. IDE "Integrated Drive Electronics" is a marketing name used
to
I never suggested that -- what I did suggest was make of_serial.c
recognize certain chip types and register them with 8250 driver.
What would be the advantage of maintaining a list of chips whose only
difference is register spacing, rather than just using reg-shift and
being done with it?
+ [EMAIL PROTECTED] {
+ compatible = "mmio-ide";
+ device_type = "ide";
Why not "ata"?
The hardware is called (E)IDE, the protocol is called ATA.
Or that's what I was told -- I think there's some historic
revisionism involved, too.
Also, what
+ [EMAIL PROTECTED] {
+ compatible = mmio-ide;
+ device_type = ide;
Why not ata?
The hardware is called (E)IDE, the protocol is called ATA.
Or that's what I was told -- I think there's some historic
revisionism involved, too.
Also, what mmio-ide in
I never suggested that -- what I did suggest was make of_serial.c
recognize certain chip types and register them with 8250 driver.
What would be the advantage of maintaining a list of chips whose only
difference is register spacing, rather than just using reg-shift and
being done with it?
The hardware is called (E)IDE, the protocol is called ATA.
Or that's what I was told -- I think there's some historic
revisionism involved, too.
ATA is the interface and standards for the ANSI standards based disk
attachment. IDE Integrated Drive Electronics is a marketing name used
to cover
Hello.
Vitaly Bordug wrote:
I acn undertand your complaint in the context of an OF driver
(which we don't have yet) but "mmio-ide" just means nothing to the
current driver, and it doesn't convery enough info on the
programming interface for the conceivable OF driver, it also does
need to
On Wed, 25 Jul 2007 13:46:57 -0500
Scott Wood wrote:
> Sergei Shtylyov wrote:
> >I acn undertand your complaint in the context of an OF driver
> > (which we don't have yet) but "mmio-ide" just means nothing to the
> > current driver, and it doesn't convery enough info on the
> > programming
On Wed, 25 Jul 2007 21:06:42 +0400
Sergei Shtylyov wrote:
> Hello.
>
> Vitaly Bordug wrote:
>
> > This updates relevant platform code (freescale mpc8349itx target)
> > to make the CompactFlash work in TrueIDE mode.
>
>Erm, I'm not sure it's worth submitting the platform device driver
>
Hello, I wrote:
Also, what mmio-ide in the compat properly means in the context
of ide_platform which is able to handle both port and memory mapped
IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses,
and
the bus-specific reg format indicates whether it's mmio-space
Hello, I wrote:
Also, what mmio-ide in the compat properly means in the context
of ide_platform which is able to handle both port and memory mapped
IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses,
and
the bus-specific reg format indicates whether it's mmio-space
Hello.
Vitaly Bordug wrote:
I acn undertand your complaint in the context of an OF driver
(which we don't have yet) but mmio-ide just means nothing to the
current driver, and it doesn't convery enough info on the
programming interface for the conceivable OF driver, it also does
need to know
On Wed, 25 Jul 2007 13:46:57 -0500
Scott Wood wrote:
Sergei Shtylyov wrote:
I acn undertand your complaint in the context of an OF driver
(which we don't have yet) but mmio-ide just means nothing to the
current driver, and it doesn't convery enough info on the
programming interface
On Wed, 25 Jul 2007 21:06:42 +0400
Sergei Shtylyov wrote:
Hello.
Vitaly Bordug wrote:
This updates relevant platform code (freescale mpc8349itx target)
to make the CompactFlash work in TrueIDE mode.
Erm, I'm not sure it's worth submitting the platform device driver
for PowerPC
Scott Wood wrote:
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context
of ide_platform which is able to handle both port and memory mapped
IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses,
and
the bus-specific reg format indicates
Sergei Shtylyov wrote:
I acn undertand your complaint in the context of an OF driver (which
we don't have yet) but "mmio-ide" just means nothing to the current
driver, and it doesn't convery enough info on the programming interface
for the conceivable OF driver, it also does need to know at
Sergei Shtylyov wrote:
Hello.
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the bus-specific reg format
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I think we must get rid with this crap, and since this IDE register
mapping is pretty much board specific, call it something like
Hello.
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the bus-specific reg format indicates whether it's
On Wed, Jul 25, 2007 at 09:54:07PM +0400, Sergei Shtylyov wrote:
> Also, what mmio-ide in the compat properly means in the context of
> ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the
Hello, I wrote:
diff --git a/arch/powerpc/boot/dts/mpc8349emitx.dts
b/arch/powerpc/boot/dts/mpc8349emitx.dts
index db0d003..f8f0e8a 100644
--- a/arch/powerpc/boot/dts/mpc8349emitx.dts
+++ b/arch/powerpc/boot/dts/mpc8349emitx.dts
@@ -37,6 +37,15 @@
reg = < 1000>;
Vitaly Bordug wrote:
diff --git a/arch/powerpc/boot/dts/mpc8349emitx.dts
b/arch/powerpc/boot/dts/mpc8349emitx.dts
index db0d003..f8f0e8a 100644
--- a/arch/powerpc/boot/dts/mpc8349emitx.dts
+++ b/arch/powerpc/boot/dts/mpc8349emitx.dts
@@ -37,6 +37,15 @@
reg = < 1000>;
Hello.
Vitaly Bordug wrote:
This updates relevant platform code (freescale mpc8349itx target)
to make the CompactFlash work in TrueIDE mode.
Erm, I'm not sure it's worth submitting the platform device driver for
PowerPC at this point, but well...
Signed-off-by: Anton Vorontsov <[EMAIL
This updates relevant platform code (freescale mpc8349itx target)
to make the CompactFlash work in TrueIDE mode.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc8349emitx.dts|9
This updates relevant platform code (freescale mpc8349itx target)
to make the CompactFlash work in TrueIDE mode.
Signed-off-by: Anton Vorontsov [EMAIL PROTECTED]
Signed-off-by: Vitaly Bordug [EMAIL PROTECTED]
---
arch/powerpc/boot/dts/mpc8349emitx.dts|9
Hello.
Vitaly Bordug wrote:
This updates relevant platform code (freescale mpc8349itx target)
to make the CompactFlash work in TrueIDE mode.
Erm, I'm not sure it's worth submitting the platform device driver for
PowerPC at this point, but well...
Signed-off-by: Anton Vorontsov [EMAIL
Vitaly Bordug wrote:
diff --git a/arch/powerpc/boot/dts/mpc8349emitx.dts
b/arch/powerpc/boot/dts/mpc8349emitx.dts
index db0d003..f8f0e8a 100644
--- a/arch/powerpc/boot/dts/mpc8349emitx.dts
+++ b/arch/powerpc/boot/dts/mpc8349emitx.dts
@@ -37,6 +37,15 @@
reg = 1000;
Hello, I wrote:
diff --git a/arch/powerpc/boot/dts/mpc8349emitx.dts
b/arch/powerpc/boot/dts/mpc8349emitx.dts
index db0d003..f8f0e8a 100644
--- a/arch/powerpc/boot/dts/mpc8349emitx.dts
+++ b/arch/powerpc/boot/dts/mpc8349emitx.dts
@@ -37,6 +37,15 @@
reg = 1000;
Scott Wood wrote:
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context
of ide_platform which is able to handle both port and memory mapped
IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses,
and
the bus-specific reg format indicates
Sergei Shtylyov wrote:
I acn undertand your complaint in the context of an OF driver (which
we don't have yet) but mmio-ide just means nothing to the current
driver, and it doesn't convery enough info on the programming interface
for the conceivable OF driver, it also does need to know at
Sergei Shtylyov wrote:
Hello.
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the bus-specific reg format
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I think we must get rid with this crap, and since this IDE register
mapping is pretty much board specific, call it something like
On Wed, Jul 25, 2007 at 09:54:07PM +0400, Sergei Shtylyov wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the
Hello.
Scott Wood wrote:
Also, what mmio-ide in the compat properly means in the context of
ide_platform which is able to handle both port and memory mapped IDE.
I/O-space is only valid in the context of PCI, ISA, or similar buses, and
the bus-specific reg format indicates whether it's
38 matches
Mail list logo
