From: Lucas Vergnettes <lucas@promac.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: LinuxPPC and BTTV : new things
Date: Mon, 1 May 1995 21:12:00 +0200 [thread overview]
Message-ID: <199905192225.AAA13560@wanadoo.fr> (raw)
In-Reply-To: <199904140459.XAA29688@lists.linuxppc.org>
Hi!
I'm not a developper, but I would like you to note that the maintainer of bttv
(driver for TV cards), has integrated PPC changes.
Unfortunately, I'm unable to debug his code which actually doesn't compiles for
apparently ridiculous reasons.
That would be nice from one of you to help him.
Email of the developper : rjkm@thp.Uni-Koeln.DE
Thanks
Lucas
--
Lucas Vergnettes -- Osteopathy Student -- mailto:lucas@promac.org
LinuxPPC, Ostéopathie et astuces telnet sur http://lucas.promac.org
EMACS : Escape-Meta-Alt-Control-Shift
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
parent reply other threads:[~1995-05-01 19:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199904140459.XAA29688@lists.linuxppc.org>]
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=199905192225.AAA13560@wanadoo.fr \
--to=lucas@promac.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).