| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1237482776.5359.89.camel@dax.rpnet.com> Date: Thu, 19 Mar 2009 17:12:56 +0000 From: Richard Purdie <rpurdie@...ux.intel.com> To: Sindhudweep Sarkar <sindhudweep.sarkar@...il.com> Cc: Greg KH <greg@...ah.com>, David Airlie <airlied@...ux.ie>, dri-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org, Thomas Hellstrom <thellstrom@...are.com> Subject: Re: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes On Thu, 2009-03-19 at 12:03 -0400, Sindhudweep Sarkar wrote: > This might be the opinion of a completely non educated end user but it > seems that an intel specific drm and other bits (xorg, mesa) would be > somewhat of a maintenance waste. > > TI-OMAP 3xxx and a couple of other arm processors use similar SGX-5xx > graphics cores. IIRC arm is often little endian so perhaps a unified > driver would be easier in the long term. Long term a unified driver would be very nice to have and nobody disagrees with that. Things don't happen overnight and you have to take smaller steps to get there. This proposal is one step on a road that may lead to a driver for the TI part too. It will need someone in the ARM community to step up and write the ARM specific bits. Cheers, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists