Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Nov 2003 11:40:54 -0500
From:      Anthony Schneider <anthony@x-anthony.com>
To:        Yuriy Tsibizov <Yuriy.Tsibizov@gfk.ru>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Sound Blaster Audigy LS problem
Message-ID:  <20031104164054.GA47060@x-anthony.com>
In-Reply-To: <C192C8912E798F4399668791C8965190674F5F@mx.hhp.local>
References:  <C192C8912E798F4399668791C8965190674F5F@mx.hhp.local>

next in thread | previous in thread | raw e-mail | index | archive | help

--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Well, it appears from your page that this driver will not work on
5.1-RELEASE (as stated from i guess 2003-10-19).  I tried building your
driver (on 5.1-RELEASE-p10), and it seemed that i just needed to add

#define PCIR_BARS 0x10
#define PCIR_BAR(x)(PCIR_BARS + (x) * 4)

and also strip (yes, bad) some arguments from busdma_tag_create() to=20
successfully build.  are these differences (addition of PCIR_BAR and=20
PCI_BARS macros and altered prototype of busdma_tag_create()) ones that
we can expect to be moving *towards* in -CURRENT, or are they ones we=20
have moved away from with -RELEASE?

also, do you think that by just redefining the PCI id to match my card's
PCI id for EMU10K2 would fix my problem if the lockfunc and lockarg
were returned back to to busdma_tag_create() (assuming i moved to
-CURRENT where I expect they currently reside)?  do you perhaps know
if the audigy ls card uses an audigy 2 chipset?  after much searching
i could not find any datasheet-style information on the audigy ls
beyond the usual frequency and decibel measurements on creative's
specification link on the product page for this card.

thank you very much for your response.
-Anthony.

On Tue, Nov 04, 2003 at 10:26:53AM +0300, Yuriy Tsibizov wrote:
> > Dear @hackers,
> > 	i recently bought a soundblaster audigy ls card hoping that it
> > would "just work" with freebsd, but sadly this is not the=20
> > case.=20
>=20
> Anthony,
>=20
> Audigy is not supported in -CURRENT kernel, but there are some patches
> to make it work under FreeBSD. I know about five of them:=20
> 1)
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D664373+686499+/usr/local/www
> /db/text/2003/freebsd-hackers/20030216.freebsd-hackers+raw old patch by
> Orlando Bassotto
> 2) http://mad.ieo-research.it/ also by Orlando=20
> 3)
> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D2034341+0+archive/2003/free
> bsd-current/20030608.freebsd-current+raw mail from David O'Brien with
> patches he use.=20
> 4) http://chibis.persons.gfk.ru/audigy/ mine
> 5) http://chibis.persons.gfk.ru/audigy/alexander/audigy_pack.tgz old
> patches for 4.x and early 5.0 kernels by Alexander Kurilovich=20
>=20
> > /sys/dev/sound/pci/emu10k1.c defines the following:
> >=20
> > #define EMU10K1_PCI_ID  0x00021102
> > #define EMU10K2_PCI_ID  0x00041102
> >=20
> It only knows about PCI IDs. In-kernel driver cannot initialize and
> control Audigy cards.
>=20
> > P.S. FreeBSD pickle 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10=20
> > #0: Mon Nov  3 19:10:54 EST 2003    =20
> > anthony@pickle:/usr/src/sys/i386/compile/PICKLE  i386
> >=20
>=20
>=20
> Yuriy Tsibizov,
> http://chibis.persons.gfk.ru
>=20

--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE/p9aVKUeW47UGY2kRAnV2AJ9l72MWhqx9uhEDYdtbghHncJGSTwCeO49z
sLbjuOyvTMm5w85q7tKO3Rw=
=kuV8
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104164054.GA47060>