From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Minimal support for dm814x
Date: Mon, 9 Nov 2015 07:06:03 -0800 [thread overview]
Message-ID: <20151109150602.GR3199@atomide.com> (raw)
In-Reply-To: <4999BB3D-4BB5-4F7C-96D7-FB687725CDCC@audioscience.com>
Hi,
* Delio Brignoli <dbrignoli@audioscience.com> [151105 05:10]:
> Hello Tony,
>
> We use dm814x in some of our products with a kernel based on version 2.6.37 modified by TI and are considering moving to a current kernel version. I recently saw this <http://lists.infradead.org/pipermail/linux-arm-kernel/2015-June/348444.html> and I?d like to try getting our board to boot as a first step and then take it from there.
> We aim at eventually having remoteproc working (at least for the DSP) and to port fixes/features we added to our 2.6.37 based tree [2].
OK great. Once you post some patches, I'm sure other people will start helping
with the effort too.
> The temporary testing branch [1] mentioned in your original message is not longer available, does that mean I can just use the master branch of <https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git> for my tests? Which toolchain did you use to build your test kernel for the hp t410?
It's now merged to mainline v4.3, so whatever is the current latest tagged
mainline kernel release (v4.3 currently) is the one to use from now on
natually :) The PLL support is still missing, so it relies on the bootloader
configured PLL values for now. I'm hoping to post PLL support patches over
next few weeks and then we can have that and more devices working for v4.5.
> I wonder if there is anyone on this list already working on getting dm814x fully working or interested in cooperating towards this goal.
Yes for sure. I've also addes linux-omap list to Cc.
Regards,
Tony
> [1] <https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=tmp-testing-dm814x-2015-06-03>
> [2] <https://github.com/audioscience/linux-omap3/tree/asi1230-upstream-tracking>
next prev parent reply other threads:[~2015-11-09 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 13:08 Minimal support for dm814x Delio Brignoli
2015-11-09 15:06 ` Tony Lindgren [this message]
2015-11-10 8:50 ` Matthijs van Duin
2015-11-10 10:23 ` Delio Brignoli
2015-11-10 10:44 ` Matthijs van Duin
2015-11-11 17:40 ` Tony Lindgren
2015-11-12 9:20 ` Matthijs van Duin
2015-11-12 17:41 ` Tony Lindgren
2015-11-13 7:14 ` Matthijs van Duin
2015-11-13 10:59 ` Matthijs van Duin
2015-11-13 14:52 ` Tony Lindgren
2015-11-13 14:57 ` Tony Lindgren
2015-11-18 5:22 ` Matthijs van Duin
2015-11-18 8:26 ` Delio Brignoli
2015-11-18 10:01 ` Matthijs van Duin
2015-11-18 11:09 ` Delio Brignoli
2015-11-10 10:05 ` Delio Brignoli
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=20151109150602.GR3199@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).