On 7 February 2013 05:51, Peter Crosthwaite
wrote:
> Currently, M25P80 uses an object property to differentiate between flash
> parts.
> Changed this over to use QOM sub-classes - the actual names of the different
> parts
> are used to create a set of dynamic classes which passes the part info a
Ping
On Tue, Feb 19, 2013 at 5:50 PM, Peter Crosthwaite
wrote:
> Hi Peter, Edgar,
>
> Can we get a merge of this either individually or as part of the next
> arm-devs? If not I will create a [PULL] but I'm guessing singles like
> this are better to go via a patch queue.
>
> Regards,
> Peter
>
> O
Hi Peter, Edgar,
Can we get a merge of this either individually or as part of the next
arm-devs? If not I will create a [PULL] but I'm guessing singles like
this are better to go via a patch queue.
Regards,
Peter
On Thu, Feb 7, 2013 at 8:40 PM, Andreas Färber wrote:
> Am 07.02.2013 06:51, schri
On Thu, Feb 7, 2013 at 8:40 PM, Andreas Färber wrote:
> Am 07.02.2013 06:51, schrieb Peter Crosthwaite:
>> Currently, M25P80 uses an object property to differentiate between flash
>> parts.
>> Changed this over to use QOM sub-classes - the actual names of the different
>> parts
>> are used to cr
Am 07.02.2013 06:51, schrieb Peter Crosthwaite:
> Currently, M25P80 uses an object property to differentiate between flash
> parts.
> Changed this over to use QOM sub-classes - the actual names of the different
> parts
> are used to create a set of dynamic classes which passes the part info as
>
Currently, M25P80 uses an object property to differentiate between flash parts.
Changed this over to use QOM sub-classes - the actual names of the different
parts
are used to create a set of dynamic classes which passes the part info as class
data. The object no longer needs to search the known_de
