public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Richard Copeman" <richard.copeman@lauterbach.co.uk>
To: linux-omap-open-source@linux.omap.com
Subject: DSP gateway build problems with 2.6.13.4
Date: Tue, 13 Dec 2005 14:59:07 -0000	[thread overview]
Message-ID: <004501c5fff5$c47e5050$642aa8c0@BUFFY> (raw)
In-Reply-To: <20051212180004.8514480695@linux.omap.com>

Hi Everyone,

I suspect that much of this is down to my lack of understanding.

I have a 2.6.13.4 kernel which I can build and which runs nicely on my OMAP
5912 OSK board.

I downloaded dspgateway 3.3 and it comes with a patch from 2.6.12-omap1.
Some of the pathnames have been changed from here to 2.6.13.4. I don't know
enough yet to know which bits need patching to what level to get something
that I can build and run. Does anybody have a patch which I can apply to my
2.6.13.4 tree (preferably with idiot proof instructions for applying said
patch too :-) ) please?

Many thanks,

Richard.

       reply	other threads:[~2005-12-13 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051212180004.8514480695@linux.omap.com>
2005-12-13 14:59 ` Richard Copeman [this message]
2005-12-14 22:07   ` DSP gateway build problems with 2.6.13.4 Matthew Percival
     [not found] <20051215103840.EF9D08062E@linux.omap.com>
2005-12-15 11:37 ` Richard Copeman
2005-12-15 11:45   ` Ishigami
2005-12-15 12:12     ` Richard Copeman
2005-12-15 22:38       ` Matthew Percival
2005-12-16  1:40       ` Ishigami
2005-12-19 10:22         ` Richard Copeman
2005-12-19 11:11           ` Ishigami
2005-12-19 14:49             ` Richard Copeman

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='004501c5fff5$c47e5050$642aa8c0@BUFFY' \
    --to=richard.copeman@lauterbach.co.uk \
    --cc=linux-omap-open-source@linux.omap.com \
    /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