public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Wolfgang Pfeiffer <roto@gmx.net>, f@pegasos.wanadoo.fr
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	debian-powerpc@lists.debian.org, debian-kernel@lists.debian.org,
	linux-kernel@vger.kernel.org
Subject: Re: [shorty: Re: 2.6.12 debian powerpc kernels and ppc64 ...]
Date: Sun, 24 Jul 2005 13:03:17 +0200	[thread overview]
Message-ID: <20050724110317.GC8804@pegasos> (raw)
In-Reply-To: <20050718203905.GC2949@localhost>

On Mon, Jul 18, 2005 at 10:39:05PM +0200, Wolfgang Pfeiffer wrote:
> The first try to send the message below didn't work. Hoping it does
> now ... :)
> 
> Regards
> Wolfgang
> 
> ----- Forwarded message from Wolfgang Pfeiifer -----
> 
> To: Sven Luther <sven.luther@wanadoo.fr>
> Cc: debian-powerpc@lists.debian.org, debian-kernel@lists.debian.org,
> 	linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12 debian powerpc kernels and ppc64 ...
> Date: Mon, 18 Jul 2005 22:17:37 +0200
> User-Agent: Mutt/1.5.9i
> X-URL: http://www.wolfgangpfeiffer.com
> 
> On Mon, Jul 18, 2005 at 07:23:05AM +0200, Sven Luther wrote:
> > On Sun, Jul 17, 2005 at 07:52:30PM +0200, Wolfgang Pfeiffer wrote:
> > > Hi Sven
> > > 
> > > On Fri, Jul 15, 2005 at 11:04:17PM +0200, Sven Luther wrote:
> > > > Hello,
> > > > 
> > > > I would like testers who want to test new powerpc kernels on ppc64 machines :
> > > > 
> > > > These i have uploaded here :
> > > > 
> > > >   http://people.debian.org/~luther/ppc64/kernel-image-2.6.12-sven_1_powerpc.deb
> > > 
> > > At least the latter one works here. Or at least it boots here without any probs,
> > > as it seems .. :
> > > 
> > > $ uname -a
> > > Linux debby 2.6.12-sven #1 Fri Jul 15 13:44:26 UTC 2005 ppc GNU/Linux
> > > 
> > > $ cat /proc/cpuinfo 
> > > processor       : 0
> > > cpu             : 7455, altivec supported
> > > clock           : 867MHz
> > > revision        : 0.2 (pvr 8001 0302)
> > > bogomips        : 865.18
> > > machine         : PowerBook3,5
> > > motherboard     : PowerBook3,5 MacRISC2 MacRISC Power Macintosh
> > > detected as     : 80 (PowerBook Titanium IV)
> > > pmac flags      : 0000001b
> > > L2 cache        : 256K unified
> > > memory          : 768MB
> > > pmac-generation : NewWorld
> > 
> > As was expectet, the 64bit is the one i am not sure about.
> > 
> > > But how come this kernel still does not have the necessary patches
> > > applied to run kismet: 
> > 
> > Please provide a bug report with this info, 
> 
> No. Please see:
> http://lkml.org/lkml/2004/8/27/303
> 
> As you can see I sent them a bug report once. It won't happen again in
> the foreseeable future.

Send a bug report to the debian kernel package i meant, not upstream, altough
ther policy is to follow upstream on this, there may be exceptions.

The debian kernel maintainer is a team, not just me, and sending personal mail
and nort an archived bug report, is bound to get lost in my (huge) inbox,
especially now that i am mostly offline 2 weeks.

> that page nobody seemed to be interested in the problem. IIRC I could
> not compile for weeks or perhaps even months a new 2.4 kernel version
> because of the mentioned errors.

2.4 is dead on desktop powerpc for over a year and a half now, so ...

> > i will apply as soon as i am back
> > in 2 weeks, if someone from the kernel team doesn't beat me to it.
> 
> The site for the patch I used, IIRC:
> <http://www.kismetwireless.net/download.shtml#orinoco2611>
> 
> wget http://www.kismetwireless.net/code/orinoco-2.6.12-rfmon-dragorn-1.diff
> 
> The md5sum for the latter that I have here is 
> 41fb7cec09f4de93cd2432eb1aceba92
> 
> So if yours will be different you can let me know.

Nice , but please apply this info to a debian bug report (reportbug kernel on
a running debian system).

> 
> And I applied the patch to 2.6.12. Or better: I probably patched a
> 2.6.11 (tarball) source with patch-2.6.12.bz2, and then applied the
> above orinoco patch. (Uncertainty because it's already a few weeks ago
> I compiled this kernel ... ) 
> 
> And just in case it might help someone else:
> The following snippet might serve as an example of how to compile this
> more or less wifi ready patched source [Please check for yourself in
> case I made any mistakes ... :) ... ]:
> 
> ------------------------
> tar xzvf linux-2.6.11.tar.gz
> cd linux-2.6.11/
> bzip2 -cd  /path/to/patch-2.6.12.bz2 | patch -p1
> 
> [then applying the orinoco patch from above]
> 
> cp /boot/someconfig .
> make oldconfig
> fakeroot make-kpkg clean
> 
> time MAKEFLAGS="CC=gcc-4.0"  fakeroot make-kpkg --append-to-version=-somename --revision +anothername kernel_image
> 
> or
> 
>  time MAKEFLAGS="CC=gcc-4.0"  fakeroot make-kpkg --append-to-version=+orinoco-patched --revision +050703 kernel_image
> ------------------------
> 
> HTH
> 
> Thanks for responding, Sven ... and yes: for your work, too :)
> 
> And sorry for refusing to play nice if things run ugly ..

Well, just provide a debian bug report so we can continue having this
conversation the right way.

TW, is this a different patch than the one Jens had applied back them in the
2.6.4 debian powerpc kenrel days ? And which was removed for bugginess or
something ?

Friendly,

Sven Luther


      reply	other threads:[~2005-07-24 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 20:39 [shorty: Re: 2.6.12 debian powerpc kernels and ppc64 ...] Wolfgang Pfeiffer
2005-07-24 11:03 ` Sven Luther [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=20050724110317.GC8804@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=debian-kernel@lists.debian.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=f@pegasos.wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roto@gmx.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