From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm
Date: Fri, 23 Sep 2016 08:50:00 +0200 [thread overview]
Message-ID: <87eg4bnm93.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f297e95d-443c-06e1-3430-4ab4a752e964@gmail.com> (Lothar Felten's message of "Fri, 23 Sep 2016 00:21:42 +0200")
>>>>> "Lothar" == Lothar Felten <lothar.felten@gmail.com> writes:
Hi,
> 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.
Ok, great!
>>> Uboot SD card patch:
>>> Early AM335x-evm boards can only use 1 bit communication to the SD card, on
>>> newer board revisions this might be fixed.
>>> Forcing 1 bit communication slows down the communication but will work
>>> regardless if the SD card is attached via 1 or 4 bits.
>>> If the board has a working 4 bit SD card interface, this patch can be removed,
>>> this will speed up the access.
>>
>> 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.
What is the upstream status of this? Have you discussed it on the u-boot
list? Right now, this is a hack that isn't suitable for upstream, but
how about tweaking omap_hsmmc host_cap if we are running on the evm?
As it stands, the beaglebone boards are also forced into 1bit mode even
though they don't have the problem.
>> 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, great!
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-09-23 6:50 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
2016-09-23 6:50 ` Peter Korsgaard [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=87eg4bnm93.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.