From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: shmprtd@googlemail.com
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] Add support for Realtek Media Player SoCs
Date: Sun, 21 Nov 2010 11:01:21 +0100 [thread overview]
Message-ID: <87r5efyozy.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <tkrat.a6310f0563cae06d@googlemail.com> (shmprtd@googlemail.com's message of "Sun, 21 Nov 2010 01:15:11 +0100 (CET)")
shmprtd@googlemail.com writes:
> Hi,
Hi,
Please read Documentation/SubmittingPatches. One big patch is just
impossible to review (at least for me), please split it in fewer
chunks.
>
> I added support for at least one of the Realtek "Galaxy" SoCs to recent
> 2.6.36 kernel. Most of the patch is based on existing linux-mips code and
> a 2.6.12 kernel source released by some of Realtek customers.
>
> Currently, this allows to start the kernel and setup serial console.
> Further development/porting will have to be done for additional platform
> devices.
Do you have an exact status of the different platform device support ?
How do you deal with the audio/video support (for instance firmware
loading & their rpc stuff) ?
>
> This code is tested on a Realtek Mars SoC. Commercial product name
> is rtd1073dd but cpu/soc id is 0x1283. Other SoCs (Venus,Jupiter,Neptune)
> have not been tested, yet.
Do you know the differences between the different versions and/or have
public specs of the SoCs ?
Also, I'm seeing a lot of rtd128x in the file names... Commercial name
for the Venus is rtd1261 for instance. I find this really
confusing. I would be tempted to use mach-realtek but I don't know
enough the realtek mips SoCs to say if it's a good idea.
Arnaud
next prev parent reply other threads:[~2010-11-21 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 0:15 [PATCH] Add support for Realtek Media Player SoCs shmprtd
2010-11-21 10:01 ` Arnaud Patard [this message]
[not found] ` <4CE8FA88.2020107@googlemail.com>
2010-11-21 11:40 ` Arnaud Patard
2010-11-22 0:41 ` Ralf Baechle
2010-11-22 2:24 ` Ralf Baechle
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=87r5efyozy.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=shmprtd@googlemail.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