On Thu, Feb 02, 2012 at 02:27:18PM +, Alan Cox wrote:
> > I see. For example the i810 also has a framebuffer driver. Do you see
> > a way to fix this except writing a kms driver for all legacy devices?
> > Otherwise I would leave the pci part untouched and only keep the
> > platform/USB pieces
On Thu, Feb 02, 2012 at 02:27:18PM +, Alan Cox wrote:
> > I see. For example the i810 also has a framebuffer driver. Do you see
> > a way to fix this except writing a kms driver for all legacy devices?
> > Otherwise I would leave the pci part untouched and only keep the
> > platform/USB pieces
> I see. For example the i810 also has a framebuffer driver. Do you see
> a way to fix this except writing a kms driver for all legacy devices?
> Otherwise I would leave the pci part untouched and only keep the
> platform/USB pieces which I'm admittedly more interested in.
Which is obsolete and un
On Thu, Feb 02, 2012 at 07:05:00AM -0500, David Airlie wrote:
> - Original Message -
> > From: "Sascha Hauer"
> > To: dri-devel at lists.freedesktop.org
> > Cc: "Inki Dae" , kernel at pengutronix.de
> > Sent: Thursday, 2 February, 2012 11:57
The non modesetting drm drivers currently use a handcrafted pci probe
function. This requires the drm core to keep a list of registered devices
for each driver. This series adds a probe function for the non modesetting
drivers and removes the legacy probe code. The USB and platform drivers
use the
- Original Message -
> From: "Sascha Hauer"
> To: "David Airlie"
> Cc: "Inki Dae" , kernel at pengutronix.de, dri-devel
> at lists.freedesktop.org
> Sent: Thursday, 2 February, 2012 12:34:02 PM
> Subject: Re: [PATCH] drm: cleanup device
- Original Message -
> From: "Sascha Hauer"
> To: dri-devel at lists.freedesktop.org
> Cc: "Inki Dae" , kernel at pengutronix.de
> Sent: Thursday, 2 February, 2012 11:57:52 AM
> Subject: [PATCH] drm: cleanup device registration
>
> The no
> I see. For example the i810 also has a framebuffer driver. Do you see
> a way to fix this except writing a kms driver for all legacy devices?
> Otherwise I would leave the pci part untouched and only keep the
> platform/USB pieces which I'm admittedly more interested in.
Which is obsolete and un
- Original Message -
> From: "Sascha Hauer"
> To: "David Airlie"
> Cc: "Inki Dae" , ker...@pengutronix.de,
> dri-devel@lists.freedesktop.org
> Sent: Thursday, 2 February, 2012 12:34:02 PM
> Subject: Re: [PATCH] drm: cleanup device regi
On Thu, Feb 02, 2012 at 07:05:00AM -0500, David Airlie wrote:
> - Original Message -
> > From: "Sascha Hauer"
> > To: dri-devel@lists.freedesktop.org
> > Cc: "Inki Dae" , ker...@pengutronix.de
> > Sent: Thursday, 2 February, 2012 11:57
- Original Message -
> From: "Sascha Hauer"
> To: dri-devel@lists.freedesktop.org
> Cc: "Inki Dae" , ker...@pengutronix.de
> Sent: Thursday, 2 February, 2012 11:57:52 AM
> Subject: [PATCH] drm: cleanup device registration
>
> The non modesettin
The non modesetting drm drivers currently use a handcrafted pci probe
function. This requires the drm core to keep a list of registered devices
for each driver. This series adds a probe function for the non modesetting
drivers and removes the legacy probe code. The USB and platform drivers
use the
12 matches
Mail list logo
