On 1/30/15 6:16 PM, Adrian Chadd wrote:
> Hi,
>
> Which chipset is it?
>
> Loading acpi_video causes a handful of interconnected pieces to shift
> (as IIRC at that point acpi_video also states that it wishes to take
> control of video setting, not just leave it all up to ACPI to drive
> itself.)
> I have a sort of "rough draft" of this. I've tested all the percentages
> (Ivy Bridge) and they do seem to correlate linearly (and to the
> intel_backlight userland program used by a lot of people). I haven't
> been able to test on any other hardware as I don't have it, and I don't
> know what ch
On Sun, Feb 1, 2015 at 2:47 PM, Miguel Clara wrote:
>
> On Sat, Jan 31, 2015 at 10:21 PM, Alexandr Krivulya <
> shur...@shurik.kiev.ua> wrote:
>
>> 31.01.2015 10:30, Miguel Clara пишет:
>> > On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers <
>> elizab...@interlinked.me>
>> > wrote:
>> >
>> >> On
On Sat, Jan 31, 2015 at 10:21 PM, Alexandr Krivulya
wrote:
> 31.01.2015 10:30, Miguel Clara пишет:
> > On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers <
> elizab...@interlinked.me>
> > wrote:
> >
> >> On 01/31/15 02:15, Miguel Clara wrote:
> >>> Working fine on a HP running current as I've noted
31.01.2015 10:30, Miguel Clara пишет:
> On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers
> wrote:
>
>> On 01/31/15 02:15, Miguel Clara wrote:
>>> Working fine on a HP running current as I've noted in the other thread
>>> as for the keys.
>>> This one (and most HP Pavillion models) use the Fn+F(2/3
On 01/30/15 17:16, Adrian Chadd wrote:
> Hi,
>
> Which chipset is it?
Oh, I missed this, sorry. I have an Ivy Bridge chipset.
> Loading acpi_video causes a handful of interconnected pieces to shift
> (as IIRC at that point acpi_video also states that it wishes to take
> control of video setting,
On Sat, Jan 31, 2015 at 8:19 AM, Elizabeth Myers
wrote:
> On 01/31/15 02:15, Miguel Clara wrote:
> > Working fine on a HP running current as I've noted in the other thread
> > as for the keys.
> > This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys,
> > and my Acer (and I think
On 01/31/15 02:15, Miguel Clara wrote:
> Working fine on a HP running current as I've noted in the other thread
> as for the keys.
> This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys,
> and my Acer (and I think not all are like this) use "Fn+<-/->"
If your keys work (as in, t
Working fine on a HP running current as I've noted in the other thread as
for the keys.
This one (and most HP Pavillion models) use the Fn+F(2/3) but the keys, and
my Acer (and I think not all are like this) use "Fn+<-/->"
Melhores Cumprimentos // Best Regards
---
On 30 January 2015 at 22:13, Elizabeth Myers wrote:
> On 01/30/15 23:20, Adrian Chadd wrote:
>> Do you have brightness buttons anywhere? What happens when you set it
>> through this API and then you use the backlight buttons?
>
>
> I do, but FreeBSD doesn't have the needed WMI doodads to interact
On 01/30/15 23:20, Adrian Chadd wrote:
> Do you have brightness buttons anywhere? What happens when you set it
> through this API and then you use the backlight buttons?
I do, but FreeBSD doesn't have the needed WMI doodads to interact with
this, nor do I have the needed Dell laptop doodads in th
On 30 January 2015 at 20:19, Elizabeth Myers wrote:
> On 01/30/15 17:25, Justin Hibbits wrote:
>> Would it make sense to have a generic 'backlight' driver framework
>> that we plug into? I wrote a backlight driver (well, 2, but both show
>> up as dev.backlight in sysctl) for powerpc, but if we wa
On 01/30/15 17:25, Justin Hibbits wrote:
> Would it make sense to have a generic 'backlight' driver framework
> that we plug into? I wrote a backlight driver (well, 2, but both show
> up as dev.backlight in sysctl) for powerpc, but if we want to have
> even more individual backlight drivers, I thi
On 01/30/15 19:31, Adrian Chadd wrote:
> So, this is one of the discussions that popped up in the linux side of
> things, that we will end up eventually pulling into freebsd when the
> i915 code is updated.
>
> The raw value is (a) different per setup, and (b) may be inverted to
> work correctly.
On 30 January 2015 at 17:01, Elizabeth Myers wrote:
> On 01/30/15 17:45, John Baldwin wrote:
>> On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote:
>>> On 01/30/15 09:17, John Baldwin wrote:
Humm. If the code is going to live in the drm driver, then I would
start with hanging
On 01/30/15 17:45, John Baldwin wrote:
> On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote:
>> On 01/30/15 09:17, John Baldwin wrote:
>>> Humm. If the code is going to live in the drm driver, then I would
>>> start with hanging a sysctl off of the drm device itself. (Each new-bus
>>>
On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote:
> On 01/30/15 09:17, John Baldwin wrote:
> > Humm. If the code is going to live in the drm driver, then I would
> > start with hanging a sysctl off of the drm device itself. (Each new-bus
> > device_t has a sysctl ctx you can get to h
Would it make sense to have a generic 'backlight' driver framework
that we plug into? I wrote a backlight driver (well, 2, but both show
up as dev.backlight in sysctl) for powerpc, but if we want to have
even more individual backlight drivers, I think it makes sense to make
them all look the same,
Hi,
Which chipset is it?
Loading acpi_video causes a handful of interconnected pieces to shift
(as IIRC at that point acpi_video also states that it wishes to take
control of video setting, not just leave it all up to ACPI to drive
itself.)
There's a bunch of discussion / code churn in the linux
On 01/30/15 09:17, John Baldwin wrote:
> Humm. If the code is going to live in the drm driver, then I would
> start with hanging a sysctl off of the drm device itself. (Each new-bus
> device_t has a sysctl ctx you can get to hang new nodes off of the
> device's node.)
I'm wondering if that's the
On 1/28/15 1:38 AM, Elizabeth Myers wrote:
> Hello,
>
> I want to add backlight support to the i915 driver in FreeBSD. It seems
> that two magic addresses are read and wrote from to change the backlight
> itself. It supports rather fine-level granularity all the way down to
> zero. Right now I use
Hello,
I want to add backlight support to the i915 driver in FreeBSD. It seems
that two magic addresses are read and wrote from to change the backlight
itself. It supports rather fine-level granularity all the way down to
zero. Right now I use a hacked-up userland program that reads
from/writes to
22 matches
Mail list logo
