At Thu, 19 Dec 2013 15:13:59 +0100,
David Herrmann wrote:
>
> Hi
>
> On Thu, Dec 19, 2013 at 3:03 PM, Takashi Iwai wrote:
> >> >> The "default if " only works if the config hasn't been set at
> >> >> all, yet. Even a "# CONFIG_* is unset" causes the "default" value to
> >> >> be ignored.
> >> >
Hi
On Thu, Dec 19, 2013 at 3:03 PM, Takashi Iwai wrote:
>> >> The "default if " only works if the config hasn't been set at
>> >> all, yet. Even a "# CONFIG_* is unset" causes the "default" value to
>> >> be ignored.
>> >
>> > Yes. I didn't suggest the strict dependency like below, just because
At Thu, 19 Dec 2013 14:37:35 +0100,
David Herrmann wrote:
>
> Hi
>
> On Thu, Dec 19, 2013 at 2:22 PM, Takashi Iwai wrote:
> > At Thu, 19 Dec 2013 13:36:38 +0100,
> > David Herrmann wrote:
> >>
> >> Hi
> >>
> >> On Thu, Dec 19, 2013 at 12:06 PM, Takashi Iwai wrote:
> >> > At Thu, 19 Dec 2013 11:
Hi
On Thu, Dec 19, 2013 at 2:22 PM, Takashi Iwai wrote:
> At Thu, 19 Dec 2013 13:36:38 +0100,
> David Herrmann wrote:
>>
>> Hi
>>
>> On Thu, Dec 19, 2013 at 12:06 PM, Takashi Iwai wrote:
>> > At Thu, 19 Dec 2013 11:46:51 +0100,
>> > David Herrmann wrote:
>> >>
>> >> Hi
>> >>
>> >> On Thu, Dec 19
At Thu, 19 Dec 2013 13:36:38 +0100,
David Herrmann wrote:
>
> Hi
>
> On Thu, Dec 19, 2013 at 12:06 PM, Takashi Iwai wrote:
> > At Thu, 19 Dec 2013 11:46:51 +0100,
> > David Herrmann wrote:
> >>
> >> Hi
> >>
> >> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
> >> wrote:
> >> >> > That bug
* David Herrmann wrote:
> Hi
>
> On Thu, Dec 19, 2013 at 1:31 PM, Ingo Molnar wrote:
> >
> > * David Herrmann wrote:
> >
> >> Hi
> >>
> >> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
> >> wrote:
> >> >> > That bug always existed, simplefb is just the first driver to hit it
> >> >> >
Hi
On Thu, Dec 19, 2013 at 1:31 PM, Ingo Molnar wrote:
>
> * David Herrmann wrote:
>
>> Hi
>>
>> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
>> wrote:
>> >> > That bug always existed, simplefb is just the first driver to hit it
>> >> > (vesafb/efifb didn't use resources). I'm aware of
Hi
On Thu, Dec 19, 2013 at 12:06 PM, Takashi Iwai wrote:
> At Thu, 19 Dec 2013 11:46:51 +0100,
> David Herrmann wrote:
>>
>> Hi
>>
>> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
>> wrote:
>> >> > That bug always existed, simplefb is just the first driver to hit it
>> >> > (vesafb/efifb
* David Herrmann wrote:
> Hi
>
> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
> wrote:
> >> > That bug always existed, simplefb is just the first driver to hit it
> >> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a
> >> > workaround you can simply disable CONFIG
At Thu, 19 Dec 2013 11:46:51 +0100,
David Herrmann wrote:
>
> Hi
>
> On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
> wrote:
> >> > That bug always existed, simplefb is just the first driver to hit it
> >> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a
> >> > workar
Hi
On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes
wrote:
>> > That bug always existed, simplefb is just the first driver to hit it
>> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a
>> > workaround you can simply disable CONFIG_X86_SYSFB. That restores
>> > the old be
> > That bug always existed, simplefb is just the first driver to hit it
> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a
> > workaround you can simply disable CONFIG_X86_SYSFB. That restores
> > the old behavior.
>
> This looks like a regression, so we'll either need a
At Wed, 18 Dec 2013 11:21:46 +0100,
David Herrmann wrote:
>
> Hi
>
> On Wed, Dec 18, 2013 at 11:17 AM, Takashi Iwai wrote:
> > At Wed, 18 Dec 2013 09:44:35 +0100,
> > Takashi Iwai wrote:
> >>
> >> At Wed, 18 Dec 2013 09:21:28 +0100,
> >> David Herrmann wrote:
> >> >
> >> > Hi
> >> >
> >> > On We
Hi
On Wed, Dec 18, 2013 at 11:17 AM, Takashi Iwai wrote:
> At Wed, 18 Dec 2013 09:44:35 +0100,
> Takashi Iwai wrote:
>>
>> At Wed, 18 Dec 2013 09:21:28 +0100,
>> David Herrmann wrote:
>> >
>> > Hi
>> >
>> > On Wed, Dec 18, 2013 at 8:42 AM, Takashi Iwai wrote:
>> > > Hi,
>> > >
>> > > with the re
At Wed, 18 Dec 2013 09:44:35 +0100,
Takashi Iwai wrote:
>
> At Wed, 18 Dec 2013 09:21:28 +0100,
> David Herrmann wrote:
> >
> > Hi
> >
> > On Wed, Dec 18, 2013 at 8:42 AM, Takashi Iwai wrote:
> > > Hi,
> > >
> > > with the recent enablement of simplefb on x86, cirrusdrmfb on QEMU/KVM
> > > gets
* David Herrmann wrote:
> Hi
>
> On Wed, Dec 18, 2013 at 8:42 AM, Takashi Iwai wrote:
> > Hi,
> >
> > with the recent enablement of simplefb on x86, cirrusdrmfb on QEMU/KVM
> > gets broken now, as reported at:
> > https://bugzilla.novell.com/show_bug.cgi?id=855821
> >
> > The cirrus VGA re
On Wed, Dec 18, 2013 at 9:44 AM, Takashi Iwai wrote:
>> That bug always existed, simplefb is just the first driver to hit it
>> (vesafb/efifb didn't use resources).
>
> Heh, the bug didn't "exist" because no other grabbed the resource
> before. The way the cirrus driver allocates the resource is
At Wed, 18 Dec 2013 09:21:28 +0100,
David Herrmann wrote:
>
> Hi
>
> On Wed, Dec 18, 2013 at 8:42 AM, Takashi Iwai wrote:
> > Hi,
> >
> > with the recent enablement of simplefb on x86, cirrusdrmfb on QEMU/KVM
> > gets broken now, as reported at:
> > https://bugzilla.novell.com/show_bug.cgi?i
Hi
On Wed, Dec 18, 2013 at 8:42 AM, Takashi Iwai wrote:
> Hi,
>
> with the recent enablement of simplefb on x86, cirrusdrmfb on QEMU/KVM
> gets broken now, as reported at:
> https://bugzilla.novell.com/show_bug.cgi?id=855821
>
> The cirrus VGA resource is reserved at first as "BOOTFB" in
> ar
Hi,
with the recent enablement of simplefb on x86, cirrusdrmfb on QEMU/KVM
gets broken now, as reported at:
https://bugzilla.novell.com/show_bug.cgi?id=855821
The cirrus VGA resource is reserved at first as "BOOTFB" in
arch/x86/kernel/sysfb_simplefb.c, which is taken by simplefb platform
devi
20 matches
Mail list logo
