On Wed, 17 Oct 2012 21:55:10 -0300, Rodrigo Vivi wrote:
> On Wed, Oct 17, 2012 at 4:22 PM, Daniel Vetter wrote:
>
> > On Mon, Oct 15, 2012 at 05:16:23PM -0300, Rodrigo Vivi wrote:
> > > On the worst scenario, users with new hardwares and old kernel from
> > enabling times can get black screens.
On Thu, Oct 18, 2012 at 2:55 AM, Rodrigo Vivi wrote:
> To be honest I don't like any of those i915_... all redundants i195.i915_
Yeah, unfortunately we can't kill them because tons of people set
random options they've found while googling (i915.rc6=7 anyone?) and
if we rename them, the module won
On Wed, Oct 17, 2012 at 4:22 PM, Daniel Vetter wrote:
> On Mon, Oct 15, 2012 at 05:16:23PM -0300, Rodrigo Vivi wrote:
> > On the worst scenario, users with new hardwares and old kernel from
> enabling times can get black screens.
> > So, now on, this i915_perliminary_hw_support variable shall be
On Mon, Oct 15, 2012 at 05:16:23PM -0300, Rodrigo Vivi wrote:
> On the worst scenario, users with new hardwares and old kernel from enabling
> times can get black screens.
> So, now on, this i915_perliminary_hw_support variable shall be used by all
> upcoming platforms that are still under enabli
On Tue, Oct 16, 2012 at 6:16 AM, Rodrigo Vivi wrote:
> On the worst scenario, users with new hardwares and old kernel from enabling
> times can get black screens.
> So, now on, this i915_perliminary_hw_support variable shall be used by all
> upcoming platforms that are still under enabling.
>
>
On the worst scenario, users with new hardwares and old kernel from enabling
times can get black screens.
So, now on, this i915_perliminary_hw_support variable shall be used by all
upcoming platforms that are still under enabling.
Although it is uncomfortable for developers use this extra variab
