From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder
Date: Sun, 30 May 2010 20:54:59 +0200 [thread overview]
Message-ID: <4C02B483.9080802@s5r6.in-berlin.de> (raw)
In-Reply-To: <htu993$60f$1@dough.gmane.org>
H.S. wrote:
> Stefan Richter wrote:
> <SNIP>
>> The patch was generated against the latest kernel sources but is
>> applicable with harmless line offsets to the 2.6.32.y stable kernel
>> series too. Hence it should be applicable to Debian's 2.6.32 sources as
>> well.
>>
>> H. S., could you please test this?
>
> Yes, I can give it a shot. Please pardon this basic question, should I
> be downloading the vanilla kernel source, patching it, compiling it and
> then testing it?
Either this or the sources of the Debian kernel that you are currently
running. The latter may perhaps be preferable for an easier switch
between distributed kernel and patched kernel.
> Or is there a precompiled binary available for download
> (i368 or amd64) with this patch included?
Alas not.
(I could build such a package if I had Debian myself, but I don't.)
> I admit I have never patched
> and compiled a kernel before for testing a patch. I have, however,
> compiled kernels numerous times quite a while ago (just for learning
> objectives).
OK; the patching as additional step is going to be the easiest one.
A quick web search turned up the following pointers for using a custom
kernel on Debian:
http://www.debian.org/doc/FAQ/ch-kernel.en.html
http://www.debian.org/releases/stable/i386/ch08s06.html.en
(I hope the described method provides an already configured kernel
source tree with Debian's configuration as baseline.)
Before you start compilation, save the email with the patch somewhere,
change into the top-level directory of the kernel sources, and apply the
patch with "patch -p1 < /the/path/to/the/email".
--
Stefan Richter
-=====-==-=- -=-= ====-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-05-30 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimIFRbKWYjFd56acxT2A6nnH6l3-7Q_UyORnonW@mail.gmail.com>
[not found] ` <4C017477.8000008@s5r6.in-berlin.de>
[not found] ` <4C0284E7.3050803@s5r6.in-berlin.de>
2010-05-30 17:43 ` Stefan Richter
2010-05-30 17:56 ` Stefan Richter
[not found] ` <htu993$60f$1@dough.gmane.org>
2010-05-30 18:54 ` Stefan Richter [this message]
[not found] ` <htuebt$l80$1@dough.gmane.org>
2010-05-31 15:14 ` H.S.
[not found] ` <hu22tj$ne4$1@dough.gmane.org>
2010-06-02 18:26 ` Stefan Richter
2010-06-02 23:23 ` H.S.
[not found] ` <20101120202044.283f1212@stein>
[not found] ` <20110112151921.0a363daa@stein>
2011-01-15 17:19 ` [PATCH] firewire: core: fix unstable I/O with Canon camcorder Stefan Richter
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=4C02B483.9080802@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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®