From: Matthew Percival <matthew@capgo.com>
To: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: Re: Linux DSP Tools for 2.6 kernel
Date: Thu, 16 Mar 2006 09:06:04 +1100 [thread overview]
Message-ID: <1142460365.9059.4.camel@localhost.localdomain> (raw)
In-Reply-To: <7e6cc7550603150327o65edee63k61bbfd982f941856@mail.gmail.com>
G'Day,
> In the "Linux DSP Tools getting Started guide", the
> Montavista linux kernel is referred for building the tools. I like to
> develop Linux DSP Tools environment compatible for open source
> 2.6.8kernel,which in not referred in the guide. Have anyone faced this
> problem?.
I installed the Linux DSP Tools without having MontaVista: there are no
related issues. I am not sure whether DSP/BIOS Link would work with 2.6
or not (I use DSP Gateway), but I have had no trouble with the DSP
compiler and other tools. I just followed the steps in chapter two of
the `Getting Started' guide and it all went smoothly.
-- Matthew
prev parent reply other threads:[~2006-03-15 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 11:27 Linux DSP Tools for 2.6 kernel naga rajan
2006-03-15 22:06 ` Matthew Percival [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=1142460365.9059.4.camel@localhost.localdomain \
--to=matthew@capgo.com \
--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