Date: Fri, 6 Jan 2006 07:45:17 +0800 From: Ariff Abdullah <ariff@FreeBSD.org> To: Zahemszky =?ISO-8859-1?Q?G=E1bor?= <Gabor@Zahemszky.HU> Cc: freebsd-multimedia@FreeBSD.org Subject: Re: snd_mss problem Message-ID: <20060106074517.2308d0a7.ariff@FreeBSD.org> In-Reply-To: <43BD88B2.7030701@Zahemszky.HU> References: <43BB0835.3070508@Zahemszky.HU> <20060104201105.3af401a9.ariff@FreeBSD.org> <43BC1856.4070305@Zahemszky.HU> <20060105071318.1e3edd45.ariff@FreeBSD.org> <43BCB6A2.3060100@Zahemszky.HU> <20060105152050.61335a21.ariff@FreeBSD.org> <43BD88B2.7030701@Zahemszky.HU>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, 05 Jan 2006 21:59:30 +0100 Zahemszky Gábor <Gabor@Zahemszky.HU> wrote: > I think, the main problem is what I wrote in the first letter: that > snd_mss recognised port 0x534 in FBSD-5, but port 0x600 in FBSD-6. > Isn't it the programming mistake, you said? > > From my first letter: > > In 5-STABLE, it's recognised by the snd-mss module. If I kldload it, > I got: > > pcm1: <CS423x> at port 0x220-0x22f,0x388-0x38b,0x534-0x537 irq 5 drq > 0,1 on isa0 > --------------------------------------------------^ > > But on FreeBSD6, the builtin chip "locks" the machine. If I kldload > snd_mss (with verbose mode), I got the following lines: > > pcm1: <CS423x> at port 0x600-0x603,0x388-0x38b,0x220-0x22f irq 5 drq > 1,0 on isa0 > --------------------------^ > I wonder if adding hint.pcm.1.port="0x534" in /boot/device.hints will make any differences (or using kenv(1)). -- Ariff Abdullah FreeBSD [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDva+Slr+deMUwTNoRAkx7AJ9TUwGXoHcTwJ0GDKNsGGujtsNI2QCfRJ0w 1uhnp0VnpplzCpfBV90DT1c= =qGnN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060106074517.2308d0a7.ariff>