From: Quinn Harris <quinn@nmt.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.3-pre1 emu10k1
Date: 18 Jan 2002 10:53:36 -0700 [thread overview]
Message-ID: <1011376417.644.0.camel@quinn.rcn.nmt.edu> (raw)
In-Reply-To: <20020117103204.GA8938@profive.com>
In-Reply-To: <20020117103204.GA8938@profive.com>
Change the MINOR(...) to minor(&...) on that line. There might be a few
more like that.
This worked for the cvs emu10k1 audigy branch for me.
The 2.5.x kernels are working toward a better way of managing device
identifiers. kdev_t is now a structure not a short. MINOR(x) is a
macro that wants a short, just like its always been. But minor(x) is an
inlined function that wants a pointer to the new kdev_t struct and
returns a char representing the device minor number. I expect MINOR
will be depreciated.
Quinn Harris
On Thu, 2002-01-17 at 03:32, Mathias Wiklander wrote:
> When I try to compile emu10k1 as a module i get this error.
>
> gcc -D__KERNEL__ -I/usr/src/v2.5.2/linux/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-
> strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686
> -DMODULE -DEMU10K1_SEQUENCER -c -o audio.o a
> udio.c
> audio.c: In function \x05mu10k1_audio_open':
> audio.c:1101: invalid operands to binary &
> make[3]: *** [audio.o] Error 1
> make[3]: Leaving directory /usr/src/v2.5.2/linux/drivers/sound/emu10k1'
>
> /Eastbay
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-01-18 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 10:32 Mathias Wiklander
2002-01-18 17:53 ` Quinn Harris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1011376417.644.0.camel@quinn.rcn.nmt.edu \
--to=quinn@nmt.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®