Gleb Natapov writes:
> On Sat, Nov 06, 2010 at 10:01:25AM +0100, Markus Armbruster wrote:
> [skip]
>> > Why should Seabios match against three (or even more) different type of
>> > devices to detect ata interface? Why require Seabios changes when this
>> > can be avoided (if new device that provi
On Sat, Nov 06, 2010 at 10:01:25AM +0100, Markus Armbruster wrote:
[skip]
> > Why should Seabios match against three (or even more) different type of
> > devices to detect ata interface? Why require Seabios changes when this
> > can be avoided (if new device that provide ata is added)? OpenBIOS als
Gleb Natapov writes:
> On Fri, Nov 05, 2010 at 05:24:01PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
>> >> Gleb Natapov writes:
>> >>
>> >> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wro
On Fri, Nov 05, 2010 at 05:24:01PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
> >> Gleb Natapov writes:
> >>
> >> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
> >> >> Gleb Natapov write
Gleb Natapov writes:
> On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
>> >> Gleb Natapov writes:
>> >>
>> >> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wro
On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
> >> Gleb Natapov writes:
> >>
> >> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
> >> >> Gleb Natapov write
Gleb Natapov writes:
> On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
>> >> Gleb Natapov writes:
>> >>
>> >> > Add "deriver_name" to DeviceInfo to use in device path building
On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
> >> Gleb Natapov writes:
> >>
> >> > Add "deriver_name" to DeviceInfo to use in device path building. In
> >>
> >> Typo "deriver".
Gleb Natapov writes:
> On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > Add "deriver_name" to DeviceInfo to use in device path building. In
>>
>> Typo "deriver". Same in subject.
>>
> Heh.
>
>> > contrast to "name" "driver_name" should refer
On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > Add "deriver_name" to DeviceInfo to use in device path building. In
>
> Typo "deriver". Same in subject.
>
Heh.
> > contrast to "name" "driver_name" should refer to functionality device
> > provide
Gleb Natapov writes:
> Add "deriver_name" to DeviceInfo to use in device path building. In
Typo "deriver". Same in subject.
> contrast to "name" "driver_name" should refer to functionality device
> provides instead of particular device model like "name" does.
Why is that useful in a device pa
Add "deriver_name" to DeviceInfo to use in device path building. In
contrast to "name" "driver_name" should refer to functionality device
provides instead of particular device model like "name" does.
Signed-off-by: Gleb Natapov
---
hw/fdc.c|1 +
hw/ide/isa.c|1 +
hw/ide/piix.
12 matches
Mail list logo