From: augulis.darius@gmail.com (Darius Augulis)
To: linux-arm-kernel@lists.infradead.org
Subject: real6410 support
Date: Fri, 23 Jul 2010 22:12:03 +0300 [thread overview]
Message-ID: <4C49E983.1030001@gmail.com> (raw)
Hi all,
there is a nice s3c6410 board named real6410.
I would like to buy it and develop product on it.
Because it's quite expensive, before I buy it, I would like to know
about kernel support for it. Is there any differences between smdk6410
and real6410? Board manufacturer doesn't provide any schematics of this
board. I found kernel and u-boot packages for real6410 on the net:
http://code.google.com/p/real6410/source/browse/trunk/soft/s3c-linux-2.6.28-Real6410.tar.bz2
http://code.google.com/p/real6410/source/browse/trunk/soft/s3c-u-boot-1.1.6-Real6410.tar.bz2
Quick look into kernel .config showed:
CONFIG_MACH_SMDK6410=y
Does it mean that I can compile main line kernel for mach-smdk6410 and I
will have all real6410 devices working?
Thanks for info!
Darius.
reply other threads:[~2010-07-23 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C49E983.1030001@gmail.com \
--to=augulis.darius@gmail.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).