On Fri, Aug 2, 2013 at 6:35 PM, Rafael J. Wysocki wrote:
> On Friday, August 02, 2013 01:58:55 PM Felipe Contreras wrote:
>> On Fri, Aug 2, 2013 at 9:03 AM, Rafael J. Wysocki wrote:
>> > On Friday, August 02, 2013 01:48:37 AM Felipe Contreras wrote:
>> >> I thin
On Fri, Aug 2, 2013 at 6:35 PM, Rafael J. Wysocki wrote:
> On Friday, August 02, 2013 01:58:55 PM Felipe Contreras wrote:
>> On Fri, Aug 2, 2013 at 9:03 AM, Rafael J. Wysocki wrote:
>> > On Friday, August 02, 2013 01:48:37 AM Felipe Contreras wrote:
>> >> I thin
not checked this issue with acpi_osi="!Windows 2012".
Please do.
--
Felipe Contreras
reasing), as if it didn't remember previous value to
> standby mode.
>
> This was something that before didn't happen.
You mean with acpi_osi="!Windows 2012"? And when you say "before",
what do you mean?
--
Felipe Contreras
not checked this issue with acpi_osi="!Windows 2012".
Please do.
--
Felipe Contreras
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
On Fri, Aug 2, 2013 at 9:03 AM, Rafael J. Wysocki wrote:
> On Friday, August 02, 2013 01:48:37 AM Felipe Contreras wrote:
>> On Fri, Aug 2, 2013 at 1:25 AM, Josep Lladonosa
>> wrote:
>> > Hello,
>> >
>> > I am using a Lenovo Edge E530 and, with kerne
reasing), as if it didn't remember previous value to
> standby mode.
>
> This was something that before didn't happen.
You mean with acpi_osi="!Windows 2012"? And when you say "before",
what do you mean?
--
Felipe Contreras
_
On Fri, Aug 2, 2013 at 9:03 AM, Rafael J. Wysocki wrote:
> On Friday, August 02, 2013 01:48:37 AM Felipe Contreras wrote:
>> On Fri, Aug 2, 2013 at 1:25 AM, Josep Lladonosa wrote:
>> > Hello,
>> >
>> > I am using a Lenovo Edge E530 and, with kernel 3.11
pretty obvious that for the time being we need to
blacklist a ton of machines so they boot without this OSI. In fact, in
might make sense to simply remove the OSI completely for all machines
(for now).
--
Felipe Contreras
pretty obvious that for the time being we need to
blacklist a ton of machines so they boot without this OSI. In fact, in
might make sense to simply remove the OSI completely for all machines
(for now).
--
Felipe Contreras
___
dri-devel mai
acpi_backlight=vendor, and the intel backlight driver doesn't work
correctly in this machine. If you are actually serious about the
mantra of "no user-space regressions", then for this machine at least,
you need to use the ACPI backlight with Windows8 OSI disabled, until
the intel backlight driver is fixed. My patch does that:
http://article.gmane.org/gmane.linux.acpi.devel/60969
--
Felipe Contreras
acpi_backlight=vendor, and the intel backlight driver doesn't work
correctly in this machine. If you are actually serious about the
mantra of "no user-space regressions", then for this machine at least,
you need to use the ACPI backlight with Windows8 OSI disabled, until
the intel backl
.linux.acpi.devel/60969
> So can the previous behavior be actually restored?
It *should*. The #1 rule of the Linux kernel is to never ever break
user-space, isn't it?
> Please keep me on CC: on replies, I'm not subscribed to the various
> lists.
You don't need to ask that in mailing lists that don't have reply-to
munged (sane ones), and vger ones don't.
Cheers.
--
Felipe Contreras
.linux.acpi.devel/60969
> So can the previous behavior be actually restored?
It *should*. The #1 rule of the Linux kernel is to never ever break
user-space, isn't it?
> Please keep me on CC: on replies, I'm not subscribed to the various
> lis
On Tue, Jan 24, 2012 at 5:54 PM, Rob Clark wrote:
> On Tue, Jan 24, 2012 at 9:33 AM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 11:24 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 2:37 PM, Felipe Contreras
>>> wrote:
>>>> On Mon, Jan 16, 2
On Tue, Jan 24, 2012 at 5:54 PM, Rob Clark wrote:
> On Tue, Jan 24, 2012 at 9:33 AM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 11:24 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 2:37 PM, Felipe Contreras
>>> wrote:
>>>> On Mon, Jan 16, 2
On Mon, Jan 16, 2012 at 11:24 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 2:37 PM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 7:01 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 10:59 AM, Felipe Contreras
>>> wrote:
>>>&g
On Mon, Jan 16, 2012 at 11:24 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 2:37 PM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 7:01 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 10:59 AM, Felipe Contreras
>>> wrote:
>>>&g
On Mon, Jan 16, 2012 at 7:01 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 10:59 AM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 6:37 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 8:12 AM, Felipe Contreras
>>> wrote:
>>>> On Fri, Jan 13
On Mon, Jan 16, 2012 at 6:37 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 8:12 AM, Felipe Contreras
> wrote:
>> On Fri, Jan 13, 2012 at 11:19 PM, Rob Clark wrote:
>>> On Fri, Jan 13, 2012 at 2:59 PM, Felipe Contreras
>>> wrote:
>>>> On Fri, Jan 13
On Fri, Jan 13, 2012 at 11:19 PM, Rob Clark wrote:
> On Fri, Jan 13, 2012 at 2:59 PM, Felipe Contreras
> wrote:
>> On Fri, Jan 13, 2012 at 10:41 PM, Rob Clark wrote:
>>> diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/plat-omap/Makefile
>>> index 9a58461..b86
On Mon, Jan 16, 2012 at 7:01 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 10:59 AM, Felipe Contreras
> wrote:
>> On Mon, Jan 16, 2012 at 6:37 PM, Rob Clark wrote:
>>> On Mon, Jan 16, 2012 at 8:12 AM, Felipe Contreras
>>> wrote:
>>>> On Fri,
On Mon, Jan 16, 2012 at 6:37 PM, Rob Clark wrote:
> On Mon, Jan 16, 2012 at 8:12 AM, Felipe Contreras
> wrote:
>> On Fri, Jan 13, 2012 at 11:19 PM, Rob Clark wrote:
>>> On Fri, Jan 13, 2012 at 2:59 PM, Felipe Contreras
>>> wrote:
>>>> On Fri,
On Fri, Jan 13, 2012 at 11:19 PM, Rob Clark wrote:
> On Fri, Jan 13, 2012 at 2:59 PM, Felipe Contreras
> wrote:
>> On Fri, Jan 13, 2012 at 10:41 PM, Rob Clark wrote:
>>> diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/plat-omap/Makefile
>>> index 9a58461..b86
obj-y := common.o sram.o clock.o devices.o dma.o mux.o \
> - ? ? ? ?usb.o fb.o counter_32k.o
> + ? ? ? ?usb.o fb.o counter_32k.o drm.o
Should be something like this:
obj-$(CONFIG_DRM_OMAP) += drm.o
No?
--
Felipe Contreras
obj-y := common.o sram.o clock.o devices.o dma.o mux.o \
> - usb.o fb.o counter_32k.o
> + usb.o fb.o counter_32k.o drm.o
Should be something like this:
obj-$(CONFIG_DRM_OMAP) += drm.o
No?
--
Felipe Contreras
___
dr
x);
> +
> ? ? ? ?/* if we aren't mapped yet, we don't need to do anything */
> ? ? ? ?if (omap_obj->block) {
> ? ? ? ? ? ? ? ?struct page **pages;
> --
Cheers.
--
Felipe Contreras
x);
> +
> /* if we aren't mapped yet, we don't need to do anything */
> if (omap_obj->block) {
> struct page **pages;
> --
Cheers.
--
Felipe Contreras
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
aces. For example, in omapfb it's
possible to use the overlays from user-space, configure some YUV
format, do vsink, and multipages just fine:
https://github.com/felipec/gst-omapfb/blob/master/omapfb.c
It's perfect to render video clips. Of course, it would be even better
if those custom interfaces were merged into the fb API.
--
Felipe Contreras
aces. For example, in omapfb it's
possible to use the overlays from user-space, configure some YUV
format, do vsink, and multipages just fine:
https://github.com/felipec/gst-omapfb/blob/master/omapfb.c
It's perfect to render video clips. Of course, it would be even better
ack will be
> appreciated. I will then work on a proof of concept and submit patches.
I also would prefer the third solution. I don't think there's much
difference from the user-space point of view, and a new ioctl would be
cleaner. Also the v4l2 fourcc's should do.
Cheers.
--
Felipe Contreras
ack will be
> appreciated. I will then work on a proof of concept and submit patches.
I also would prefer the third solution. I don't think there's much
difference from the user-space point of view, and a new ioctl would be
cleaner. Also the v4l2 fourcc's should do.
Chee
32 matches
Mail list logo
