On Fri, 2007-06-15 at 11:46 -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 15 Jun 2007, Richard Hughes wrote:
> > I'm going on a rampage of killing system daemons that talk to one type
> > of hardware. Leave those to me.
>
> Ok, but please make sure to use a spiked war hammer, coated in radio
On Fri, 15 Jun 2007, Richard Hughes wrote:
> I'm going on a rampage of killing system daemons that talk to one type
> of hardware. Leave those to me.
Ok, but please make sure to use a spiked war hammer, coated in radioactive
rabid platypus blood while at it... it always pay to make it very clear j
On Fri, 2007-06-15 at 15:09 +0100, Matthew Garrett wrote:
>
> You can, but then you need to track what the source of it was. You
> don't
> want to draw a volume notification on screen just because somebody's
> dragged a slider in the mixer window. I think tracking the keypresses
> is probably a
On Fri, Jun 15, 2007 at 03:06:28PM +0100, Richard Hughes wrote:
> But we can get this using ALSA, no?
You can, but then you need to track what the source of it was. You don't
want to draw a volume notification on screen just because somebody's
dragged a slider in the mixer window. I think track
On Fri, 2007-06-15 at 11:05 -0300, Henrique de Moraes Holschuh wrote:
>
> Note that I still intend to push for a ALSA hardware mixer interface
> to control the built-in mixer.
Totally, it's insanity any other way. This isn't a keyboard press, this
is a genuine mixer device.
Richard.
On Fri, 2007-06-15 at 14:58 +0100, Matthew Garrett wrote:
>
> No, I think the buttons should generate KEY_VOLUMEUP, KEY_VOLUMEDOWN
> and
> KEY_MUTE. Hal can then be given an fdi file that tells it that the
> Thinkpad mixer works independently of userspace (like we already do
> for
> brightness)
On Fri, 15 Jun 2007, Matthew Garrett wrote:
> On Fri, Jun 15, 2007 at 10:44:26AM -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 15 Jun 2007, Matthew Garrett wrote:
> > > This problem already has to be dealt with in brightness control, so I'd
> > > just send the keys. FWIW, it turns out that
On Fri, Jun 15, 2007 at 10:44:26AM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 15 Jun 2007, Matthew Garrett wrote:
> > This problem already has to be dealt with in brightness control, so I'd
> > just send the keys. FWIW, it turns out that slaving the volume keys to
> > the master volume a
On Fri, 15 Jun 2007, Matthew Garrett wrote:
> On Fri, Jun 15, 2007 at 10:05:15AM -0300, Henrique de Moraes Holschuh wrote:
> > I *really* don't want to see those keys mapped to something that would go
> > and increase the AC97/HDA mixer volume up, etc... btw. and I *bet* that's
> > just the kind o
On Fri, Jun 15, 2007 at 10:05:15AM -0300, Henrique de Moraes Holschuh wrote:
> I *really* don't want to see those keys mapped to something that would go
> and increase the AC97/HDA mixer volume up, etc... btw. and I *bet* that's
> just the kind of stupidity people would pull off (because they hav
On Fri, 2007-06-15 at 10:05 -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 15 Jun 2007, Richard Hughes wrote:
> > > I have a patch that fixes and documents the whole stuff almost ready, it
> > > will be pushed to the git tree soon.
> >
> > So, we still use a hardware mixer? That still makes m
On Fri, 15 Jun 2007, Richard Hughes wrote:
> > I have a patch that fixes and documents the whole stuff almost ready, it
> > will be pushed to the git tree soon.
>
> So, we still use a hardware mixer? That still makes most sense from my
> point of view as the events are still hardware.
Yes, we wil
On Fri, 2007-06-15 at 01:06 -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 29 May 2007, Matthew Garrett wrote:
> > On Mon, May 28, 2007 at 11:58:24PM +0100, Richard Hughes wrote:
> > > I've been hacking to make the nvram hardware buttons on thinkpad exposed
> > > as a hardware mixer device. Th
13 matches
Mail list logo
