Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Mike C. Ward" <mward@pioneer-pra.com>
To: "'kernel coder'" <lhrkernelcoder@gmail.com>
Cc: <linux-mips@linux-mips.org>
Subject: RE: Porting oprofile to 2.4.32 kernel
Date: Wed, 26 Oct 2005 10:25:55 -0700	[thread overview]
Message-ID: <013701c5da52$5399a9c0$5502020a@eo> (raw)
In-Reply-To: <20051026135414.GD3161@linux-mips.org>

But if you wanted to undertake that cause nonetheless, you
could check out the patch I did to 2.4.25 
at 
http://oss.pioneer-pra.com/oprofile/

Mike

> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org 
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Ralf Baechle
> Sent: Wednesday, October 26, 2005 6:54 AM
> To: kernel coder
> Cc: linux-mips@linux-mips.org
> Subject: Re: Porting oprofile to 2.4.32 kernel
> 
> 
> On Wed, Oct 26, 2005 at 02:34:07AM -0700, kernel coder wrote:
> 
> >    i'm trying to port oprofile on 2.4.32 kernel running on MIPS 
> > board.From where can i  get the patch for other boards so 
> that i can 
> > make a head start by using that patch as a guide.
> 
> Oprofile for 2.4 is considered a lost cause on any 
> architecture and I guess I'd rather do something sensible 
> like ironing snowflakes than porting it at this stage where 
> funeral eulogies for 2.4 are already being written ;-)
> 
>   Ralf
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Mike C. Ward" <mward@pioneer-pra.com>
To: 'kernel coder' <lhrkernelcoder@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: RE: Porting oprofile to 2.4.32 kernel
Date: Wed, 26 Oct 2005 10:25:55 -0700	[thread overview]
Message-ID: <013701c5da52$5399a9c0$5502020a@eo> (raw)
Message-ID: <20051026172555.VwTGkkDcL-qJHOvD549605jUbJnpI2HL_K-IFDOlty8@z> (raw)
In-Reply-To: <20051026135414.GD3161@linux-mips.org>

But if you wanted to undertake that cause nonetheless, you
could check out the patch I did to 2.4.25 
at 
http://oss.pioneer-pra.com/oprofile/

Mike

> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org 
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Ralf Baechle
> Sent: Wednesday, October 26, 2005 6:54 AM
> To: kernel coder
> Cc: linux-mips@linux-mips.org
> Subject: Re: Porting oprofile to 2.4.32 kernel
> 
> 
> On Wed, Oct 26, 2005 at 02:34:07AM -0700, kernel coder wrote:
> 
> >    i'm trying to port oprofile on 2.4.32 kernel running on MIPS 
> > board.From where can i  get the patch for other boards so 
> that i can 
> > make a head start by using that patch as a guide.
> 
> Oprofile for 2.4 is considered a lost cause on any 
> architecture and I guess I'd rather do something sensible 
> like ironing snowflakes than porting it at this stage where 
> funeral eulogies for 2.4 are already being written ;-)
> 
>   Ralf
> 
> 

  reply	other threads:[~2005-10-26 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26  9:34 Porting oprofile to 2.4.32 kernel kernel coder
2005-10-26 13:54 ` Ralf Baechle
2005-10-26 17:25   ` Mike C. Ward [this message]
2005-10-26 17:25     ` Mike C. Ward

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='013701c5da52$5399a9c0$5502020a@eo' \
    --to=mward@pioneer-pra.com \
    --cc=lhrkernelcoder@gmail.com \
    --cc=linux-mips@linux-mips.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