> -----Original Message----- > From: linux-fbdev-owner@xxxxxxxxxxxxxxx [mailto:linux-fbdev- > owner@xxxxxxxxxxxxxxx] On Behalf Of Olaf Hering > Sent: Tuesday, February 19, 2013 1:40 PM > To: Haiyang Zhang > Cc: FlorianSchandinat@xxxxxx; linux-fbdev@xxxxxxxxxxxxxxx; KY Srinivasan; > jasowang@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer > Driver > > On Tue, Feb 19, Haiyang Zhang wrote: > > > The emulated video device is a separate device from the synthetic > video. > > The synthetic driver can only take control of the synthetic video, but > not > > the emulated video. > > Please add this to the comment above. Will do. > > Actually, we already have a similar mechanism in ata/ata_piix.c to > disable > > emulated IDE drive on Hyper-V, so it won't conflict with the synthetic > drive. > > I havent read the vesafb code, but I think it can kind of give up the > hardware, something ata_piix can not do. In my test, the vesafb doesn't automatically give up the emulated video device, unless I add the DMI based mechanism to let it exit on Hyper-V. Thanks, - Haiyang _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
