On Wednesday 25 March 2009, Grant Likely wrote:
> >> This case really does sound like a driver bug and that the existing
> >> cfi-flash binding is sufficient to describe the hardware. IIUC, when
> >> all the flash chips are of the same type the physmap_of driver should
> >> be smart enough to dete
On Wed, Mar 25, 2009 at 3:35 AM, Stefan Roese wrote:
> On Tuesday 24 March 2009, Grant Likely wrote:
>> > OK, in the example above such a spanning partition is not so likely. But
>> > think about my original example, the Intel P30 with two different cfi
>> > compatible chips on one die. Here a par
On Tuesday 24 March 2009, Grant Likely wrote:
> > OK, in the example above such a spanning partition is not so likely. But
> > think about my original example, the Intel P30 with two different cfi
> > compatible chips on one die. Here a partition spanning over both devices
> > is very likely.
>
> I
On Tue, Mar 24, 2009 at 9:39 AM, Stefan Roese wrote:
> On Tuesday 24 March 2009, Grant Likely wrote:
>> >> Sounds to me like a physmap_of driver bug. I don't think there is any
>> >> advantage in changing the partition syntax since concatenated flash
>> >> will always be used as a single device.
On Tuesday 24 March 2009, Grant Likely wrote:
> >> Sounds to me like a physmap_of driver bug. I don't think there is any
> >> advantage in changing the partition syntax since concatenated flash
> >> will always be used as a single device. It doesn't make any sense to
> >> try and span partitions
On Tue, Mar 24, 2009 at 3:07 AM, Stefan Roese wrote:
> On Monday 23 March 2009, Grant Likely wrote:
>> On Mon, Mar 23, 2009 at 4:51 AM, Stefan Roese wrote:
>> > I just noticed that physmap_of can't handle multiple devices of different
>> > type described in one device node. For example the Intel
On Monday 23 March 2009, Grant Likely wrote:
> On Mon, Mar 23, 2009 at 4:51 AM, Stefan Roese wrote:
> > I just noticed that physmap_of can't handle multiple devices of different
> > type described in one device node. For example the Intel P30 48F4400
> > (64MByte) consists internally of 2 non-iden
On Mon, Mar 23, 2009 at 4:51 AM, Stefan Roese wrote:
> I just noticed that physmap_of can't handle multiple devices of different type
> described in one device node. For example the Intel P30 48F4400 (64MByte)
> consists internally of 2 non-identical NOR chips. So a "simple"
[...]
> Now the real p
I just noticed that physmap_of can't handle multiple devices of different type
described in one device node. For example the Intel P30 48F4400 (64MByte)
consists internally of 2 non-identical NOR chips. So a "simple"
fl...@0,0 {
#address-cells = <1>;
#si
