From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm
Date: Fri, 23 Sep 2016 07:47:10 +0200 [thread overview]
Message-ID: <20160923074710.4c8b372b@free-electrons.com> (raw)
In-Reply-To: <f297e95d-443c-06e1-3430-4ab4a752e964@gmail.com>
Hello,
On Fri, 23 Sep 2016 00:21:42 +0200, Lothar Felten wrote:
> I changed the patches, they now update the current beaglebone, the
> defconfigs will be: beaglebone_defconfig and beaglebone_qt_defconfig.
> The readme.txt lists the supported targets.
Sounds good.
> > Do you still have those early AM335x EVM boards? Are they widespread?
> > I'm wondering if it really makes sense to have this patch.
>
> I've only use two EVMs and they both have the issue, I'm not sure that
> it ever got fixed. Any board will run in 1 bit mode, but some evms won't
> run in 4 bit mode, so I think that's a safe choice. Anyway, it applies
> to the uboot only.
OK, let's keep this then. What worries me is that the kind of patch
that has never any chance of being removed from Buildroot. I would have
preferred a solution that could potentially be accepted upstream.
> > Does this really work for the BeagleBone, which uses ttyO2 if I
> > remember correctly? Maybe another reason to have a defconfig that
> > supports just the am335x_evm.
>
> The beaglebone (ttyO0 on USB) beagleboneblack (ttyO0 on pinheader) and
> the evm (sub d 9 pin) all use ttyO0
OK, my bad. I was probably confusing with the beagleboard where I think
it was the third serial port (ttyO2). So everything is fine.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-23 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 11:51 [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm Lothar Felten
2016-09-18 17:30 ` Thomas Petazzoni
2016-09-21 7:40 ` Peter Korsgaard
2016-09-21 8:53 ` Thomas Petazzoni
2016-09-21 9:01 ` Peter Korsgaard
2016-09-21 10:18 ` Thomas Petazzoni
2016-09-21 10:36 ` Peter Korsgaard
2016-09-21 10:55 ` Thomas Petazzoni
2016-09-21 11:23 ` Peter Korsgaard
2016-09-21 12:09 ` Thomas Petazzoni
2016-09-22 22:21 ` Lothar Felten
2016-09-23 5:47 ` Thomas Petazzoni [this message]
2016-09-23 6:50 ` Peter Korsgaard
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=20160923074710.4c8b372b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.