Date: Sat, 11 Nov 2006 09:16:38 -0500 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Julian Elischer <julian@elischer.org> Cc: Alexander@leidinger.net, re@freebsd.org, multimedia@freebsd.org, Ariff Abdullah <ariff@freebsd.org> Subject: Re: new HDA driver and 6.2? Message-ID: <1163254598.26994.7.camel@opus.cse.buffalo.edu> In-Reply-To: <455576AF.40505@elischer.org> References: <4550463E.7060903@elischer.org> <20061107171809.1d345652.ariff@FreeBSD.org> <20061107113605.bx6w8huog8kg0g8s@webmail.leidinger.net> <455063B2.3070301@elischer.org> <20061108074859.2e646836.ariff@FreeBSD.org> <455576AF.40505@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-LfZtzeve26n7y4ohCjII
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Fri, 2006-11-10 at 23:07 -0800, Julian Elischer wrote:
> Ariff Abdullah wrote:
> > On Tue, 07 Nov 2006 02:45:06 -0800
> > Julian Elischer <julian@elischer.org> wrote:
> >> Alexander Leidinger wrote:
> >>> Quoting Ariff Abdullah <ariff@FreeBSD.org> (from Tue, 7 Nov 2006=20
> >>> 17:18:09 +0800):
> >>>
> >>>> On Tue, 07 Nov 2006 00:39:26 -0800
> >>>> Julian Elischer <julian@elischer.org> wrote:
> >>>>> Will the HD driver be MFC'd before or after 6.2?
> >>>>>
> >>>> I couldn't tell yet. How about voting for this?
> >>> Is it ready already? I thought there's a lot missing (recording?).
> >>> I would expect a lot of support mails appearing for the not
> >>> working parts (more than we get for "no HDA support, please
> >>> help").
> > Nothing missing. Recording works just fine. The only problem is with
> > specific recording source (mic/line) and that only represent 5% of
> > all working hda out there. On most codecs (conexant, most adxxxx,
> > alcxxx, most stac), everything works as expected.
> >=20
> >> I guess that's the big question..
> >>
> >=20
> > My take is, this driver won't make its way into RELENG_6 at all.
>=20
> I'll push for having it in as soon as possible even 6.2, if it
> doesn't change the other drivers.
>=20
> If there are further changes to the framework then they can happen after =
6.2
>=20
The release had been blocked due to the problems with em(4) but as of a
day or so ago we are now un-blocked on that issue. Since that had been
the one thing viewed as a show-stopper and the release cycle has already
dragged on a fair bit longer than expected we'll be moving into the
Release Candidate stage very quickly, and the chances of something like
this making it into 6.2 are very small I'm afraid.
If well tested patches against RELENG_6 can be made within the next
couple of days and as long as they are very self-contained (don't wind
up touching other drivers much if at all) we'll consider letting it into
RELENG_6 before we branch for the release but it might be best to just
let this slide for 6.2 and MFC it after the release. Like I said above
we've already slipped the release schedule a fair bit, if it hadn't been
for a handful of big problems we would have released already and this
stuff would have come along too late anyway. :-)
--=20
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
--=-LfZtzeve26n7y4ohCjII
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQBFVdtG/G14VSmup/YRAtGoAJ4r8mrtgLDnO7oGyrZpGwwXFln3jQCgmLmv
Iqfr9fv8IukAhgtkgkQ9usc=
=QPfR
-----END PGP SIGNATURE-----
--=-LfZtzeve26n7y4ohCjII--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1163254598.26994.7.camel>