On Mon, Nov 17, 2008 at 11:34:01PM +0200, Alexey Suslikov wrote:
> Jacob Meuser wrote:
>
> > > I saw the suggestion to read tech@ in another thread but saw no (recent)
> > > diffs there that I believe apply to this machine.
> >
> > one thing I'm trying to do is get rid of the static mixer definiti
Jacob Meuser wrote:
> > I saw the suggestion to read tech@ in another thread but saw no (recent)
> > diffs there that I believe apply to this machine.
>
> one thing I'm trying to do is get rid of the static mixer definitions
> in azalia_codec.c. this exposes all the controls instead of a limited
On Sun, Nov 16, 2008 at 11:00:58PM +0100, Alexander Hall wrote:
> Jacob Meuser wrote:
>
>> there are more coming ... even if your device starts working, please
>> keep testing patches to make sure it doesn't stop working ;)
>
> In this regard, I've had no sound on my speakers for a few snaps, but
On Sun, Nov 16, 2008 at 09:47:55AM -0600, Marco Peereboom wrote:
> That is not in yet, right?
it's in src/sys/dev/pci/azalia_codec.c.
but it's pretty basic right now. the ALC patch I sent modifies it
a bit so we can give it hints. and that patch uses the hints to
give an outputs.master to most
Jacob Meuser wrote:
there are more coming ... even if your device starts working, please
keep testing patches to make sure it doesn't stop working ;)
In this regard, I've had no sound on my speakers for a few snaps, but
sound when headphones are plugged in. Updating to a new snap today fixed
That is not in yet, right?
On Sat, Nov 15, 2008 at 01:51:31PM +, Jacob Meuser wrote:
> On Sat, Nov 15, 2008 at 07:30:24AM -0600, Marco Peereboom wrote:
> > I find this very confusing too. I have to fart around until I figure
> > out what volume setting is which. Is there no way to generalize
On Sat, Nov 15, 2008 at 07:30:24AM -0600, Marco Peereboom wrote:
> I find this very confusing too. I have to fart around until I figure
> out what volume setting is which. Is there no way to generalize this?
>
> I mean do all this fancy stuff but provide general names that always
> routes the co
I find this very confusing too. I have to fart around until I figure
out what volume setting is which. Is there no way to generalize this?
I mean do all this fancy stuff but provide general names that always
routes the command to the proper channel. For example a master mute and
a master volume
On Sat, Nov 15, 2008 at 5:37 AM, Jacob Meuser <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 15, 2008 at 04:25:49AM +, Bryan wrote:
>> Greetings,
>>
>> I just inherited a Dell Inspiron 1520 a few days ago, and I was eager
>> to install -current on it. I installed the November 6th snapshot.
>> Sadly,
On Sat, Nov 15, 2008 at 04:25:49AM +, Bryan wrote:
> Greetings,
>
> I just inherited a Dell Inspiron 1520 a few days ago, and I was eager
> to install -current on it. I installed the November 6th snapshot.
> Sadly, I found that this laptop uses the azalia(4) driver. (my
> Inspiron 9300 uses au
10 matches
Mail list logo
