Thanks again, Daniel... I'll take a look. If the ID isn't in there,
I'll submit a PR to get it added. (should only take about 10-12
months to actually get it comitted, if experience is a reliable guide :-/)
On Sun, Sep 26, 1999 at 10:09:58PM +0200, D. Rock wrote:
> "Donald J . Maddox" schrieb:
Thanks, Doug. Peter already provided an equivalent patch, and I am
happy to report that it works like a charm (of course :-)).
On Mon, Sep 27, 1999 at 10:35:46AM +0100, Doug Rabson wrote:
> On Sun, 26 Sep 1999, Donald J . Maddox wrote:
>
> > I couldn't get my PnP Creative AWE64G to work with th
God knows, I'll second that one... :-) Hear, hear!
On Sun, Sep 26, 1999 at 07:39:27PM -0700, Darryl Okahata wrote:
> I want to publicly thank Peter Wemm for posting a reply that is
> courteous, informative, and useful. Recently, there has been too much
> noise in this and other FreeBSD lis
On Mon, Sep 27, 1999 at 05:05:37AM +0800, Peter Wemm wrote:
>
> The old PnP code was matching on the card vendor ID. The new pnp code
> treats each logical device on it's own and matches by logical ID..
> (It's actually far more useful that way as most cards have their own
> manufacturer ID but
On Sun, Sep 26, 1999 at 02:29:43PM -0700, Mike Smith wrote:
> > Again, thanks for the very helpful and informative answers. I would still
> > appreciate it if someone could give me a little bit more of a clue as to
> > what is necessary to add newPnP-awareness to the AWE driver, though.
> > (S
While your response seems a bit strong, to say the least, I confess
that the redirection was a real mistake... I thought Mike had replied
to me on the list and I had hit 'r' by accident, instead of 'g', in
mutt. My apologies to Mike.
On Sun, Sep 26, 1999 at 05:10:30PM -0400, Bill Fumerola wrote
Ok, will do. Thanks.
This may be a silly question, but... The old PnP driver recognized
a lot of devices, including my AWE64. Isn't there a list of IDs it
was aware of that should be merged into newPnP ASAP?
On Mon, Sep 27, 1999 at 04:27:42AM +0800, Peter Wemm wrote:
> Please try the followin
I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead. All I get is:
unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: at port 0x200-0x207 on isa0
unknown2: at port 0x620-0x623 on isa0
It is my
Doug Rabson wrote:
> On Mon, 27 Sep 1999, Andrew Sparrow wrote:
>
> >
> > > : case 0x31008c0e: /* CTL0031 */
> > > : case 0x41008c0e: /* CTL0041 */
> > > : case 0x42008c0e: /* CTL0042 */
> > > : + case 0x44008c0e: /* CTL0044 */
> > > : case 0x45008c0e: /* CT
On Mon, 27 Sep 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Doug Rabson
>writes:
> : case 0x31008c0e: /* CTL0031 */
> : case 0x41008c0e: /* CTL0041 */
> : case 0x42008c0e: /* CTL0042 */
> : + case 0x44008c0e: /* CTL0044 */
> :
On Mon, 27 Sep 1999, Andrew Sparrow wrote:
>
> > : case 0x31008c0e: /* CTL0031 */
> > : case 0x41008c0e: /* CTL0041 */
> > : case 0x42008c0e: /* CTL0042 */
> > : + case 0x44008c0e: /* CTL0044 */
> > : case 0x45008c0e: /* CTL0045 */
>
> > What is C
On Mon, 27 Sep 1999, Donald J . Maddox wrote:
> Thanks, Doug. Peter already provided an equivalent patch, and I am
> happy to report that it works like a charm (of course :-)).
Good. The next stage is probably to talk to the midi folks and possibly
see about porting the awe driver.
--
Doug Rab
> : case 0x31008c0e: /* CTL0031 */
> : case 0x41008c0e: /* CTL0041 */
> : case 0x42008c0e: /* CTL0042 */
> : + case 0x44008c0e: /* CTL0044 */
> : case 0x45008c0e: /* CTL0045 */
> What is CTL0043? Seems like a logical progression to me :-
Thanks, Doug. Peter already provided an equivalent patch, and I am
happy to report that it works like a charm (of course :-)).
On Mon, Sep 27, 1999 at 10:35:46AM +0100, Doug Rabson wrote:
> On Sun, 26 Sep 1999, Donald J . Maddox wrote:
>
> > I couldn't get my PnP Creative AWE64G to work with th
God knows, I'll second that one... :-) Hear, hear!
On Sun, Sep 26, 1999 at 07:39:27PM -0700, Darryl Okahata wrote:
> I want to publicly thank Peter Wemm for posting a reply that is
> courteous, informative, and useful. Recently, there has been too much
> noise in this and other FreeBSD lis
In message <[EMAIL PROTECTED]> Doug Rabson
writes:
: case 0x31008c0e: /* CTL0031 */
: case 0x41008c0e: /* CTL0041 */
: case 0x42008c0e: /* CTL0042 */
: + case 0x44008c0e: /* CTL0044 */
: case 0x45008c0e: /* CTL0045 */
What is CTL0043? Seems like a logical progression
On Sun, 26 Sep 1999, Doug wrote:
> Peter Wemm wrote:
> >
> > "Donald J . Maddox" wrote:
> > > Ok, will do. Thanks.
> > >
> > > This may be a silly question, but... The old PnP driver recognized
> > > a lot of devices, including my AWE64. Isn't there a list of IDs it
> > > was aware of that sh
On Sun, 26 Sep 1999, Donald J . Maddox wrote:
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead. All I get is:
>
> unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: at port 0x200-0x207
So who subscribed me to [EMAIL PROTECTED]? :-)
Really guys if you don't like the person or the questions he asks, don't
reply. If you really need to say something send it to /dev/null, not
even to him/her in private mail. We are here because we like FreeBSD
and use it, not to pick fights with eac
Peter Wemm <[EMAIL PROTECTED]> wrote:
> We're not doing this because we enjoy pain and suffering, it's because
> it'll be better and more robust in the long run. Unfortunately, there was
> no canonical list of logical ID's on the cards we used to recognize.
>
> So I repeat for the list.. If you
Vladimir Kushnir wrote:
> Thanks for replay, but what I am to do? At least, where to start looking?
> Card is revognized, so this indeed shouldn't be PnP fault.
> Card's 16 bit, but so far the only acceptable sound give esd or mpg123.
The person to talk to is Cameron Grant <[EMAIL PROTECTED]> for
Thanks for replay, but what I am to do? At least, where to start looking?
Card is revognized, so this indeed shouldn't be PnP fault.
Card's 16 bit, but so far the only acceptable sound give esd or mpg123.
On Mon, 27 Sep 1999, Peter Wemm wrote:
> Vladimir Kushnir wrote:
> > Hello, here's an outpu
Vladimir Kushnir wrote:
> Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
> perfectly all right as css device & friends under old Pnp & VoxWare, but
> now outputs very poor sound through /dev/dsp and no sound at all when
> playing audio CD, and of course no midi):
>
> dmesg:
Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
perfectly all right as css device & friends under old Pnp & VoxWare, but
now outputs very poor sound through /dev/dsp and no sound at all when
playing audio CD, and of course no midi):
dmesg:
pcm0: at port
0x220-0x22f,0x530-0x5
Doug wrote:
> Peter Wemm wrote:
> >
> > "Donald J . Maddox" wrote:
> > > Ok, will do. Thanks.
> > >
> > > This may be a silly question, but... The old PnP driver recognized
> > > a lot of devices, including my AWE64. Isn't there a list of IDs it
> > > was aware of that should be merged into ne
> > The old PnP code was matching on the card vendor ID. The new pnp code
> > treats each logical device on it's own and matches by logical ID.
>
> The new architecture sounds like a good thing, but isn't there a way to
> fall back to the old method if the logical device ID isn't found?
>
Peter Wemm wrote:
>
> "Donald J . Maddox" wrote:
> > Ok, will do. Thanks.
> >
> > This may be a silly question, but... The old PnP driver recognized
> > a lot of devices, including my AWE64. Isn't there a list of IDs it
> > was aware of that should be merged into newPnP ASAP?
>
> The old PnP
While your response seems a bit strong, to say the least, I confess
that the redirection was a real mistake... I thought Mike had replied
to me on the list and I had hit 'r' by accident, instead of 'g', in
mutt. My apologies to Mike.
On Sun, Sep 26, 1999 at 05:10:30PM -0400, Bill Fumerola wrote
Considering you just redirected what seemed to be a private message
to a public mailing list, I have completely just written you off.
To say this is bad etiquette would be a gross understatement. I hope
you feel like a complete ass, because you just presented yourself as
one.
--
- bill fumerol
On Sun, Sep 26, 1999 at 02:29:43PM -0700, Mike Smith wrote:
> > Again, thanks for the very helpful and informative answers. I would still
> > appreciate it if someone could give me a little bit more of a clue as to
> > what is necessary to add newPnP-awareness to the AWE driver, though.
> > (S
On Mon, Sep 27, 1999 at 05:05:37AM +0800, Peter Wemm wrote:
>
> The old PnP code was matching on the card vendor ID. The new pnp code
> treats each logical device on it's own and matches by logical ID..
> (It's actually far more useful that way as most cards have their own
> manufacturer ID but
"Donald J . Maddox" wrote:
> Ok, will do. Thanks.
>
> This may be a silly question, but... The old PnP driver recognized
> a lot of devices, including my AWE64. Isn't there a list of IDs it
> was aware of that should be merged into newPnP ASAP?
The old PnP code was matching on the card vendor
Ok, will do. Thanks.
This may be a silly question, but... The old PnP driver recognized
a lot of devices, including my AWE64. Isn't there a list of IDs it
was aware of that should be merged into newPnP ASAP?
On Mon, Sep 27, 1999 at 04:27:42AM +0800, Peter Wemm wrote:
> Please try the followin
"Donald J . Maddox" wrote:
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead. All I get is:
>
> unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 o
n isa0
> unknown1: at port 0x200-0x207 on isa0
> unkno
Thanks again, Daniel... I'll take a look. If the ID isn't in there,
I'll submit a PR to get it added. (should only take about 10-12
months to actually get it comitted, if experience is a reliable guide :-/)
On Sun, Sep 26, 1999 at 10:09:58PM +0200, D. Rock wrote:
> "Donald J . Maddox" schrieb:
"Donald J . Maddox" schrieb:
>
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead. All I get is:
>
> unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: at port 0x200-0x207 on isa0
> unkno
I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead. All I get is:
unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: at port 0x200-0x207 on isa0
unknown2: at port 0x620-0x623 on isa0
It is my
37 matches
Mail list logo
