Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] microcom broken with latest uclibc snapshot.
Date: Tue, 23 Jan 2007 10:06:16 +0100	[thread overview]
Message-ID: <004a01c73ed1$21643210$01c4af0a@atmel.com> (raw)
In-Reply-To: 20070123001856.GA10178@aon.at

Bernhard Fischer wrote:
> On Tue, Jan 23, 2007 at 12:32:37AM +0100, Ulf Samuelsson wrote:
>> When using the latest uClibc snapshot to build the toolchain,
>> It looks like the high speeds are not acceptable (> 1151200)
>> and the generated <staging_dir>/arm-linux/sys-include/bits/termios.h
>> has higher speeds commented away.
>>
>> #if 0 /* limited on uClibc, keep in sync w/ cfsetspeed.c */
>> #define B230400 0010003
>> ...
>> #endif
>>
>> This is not a good idea, if the MCU can handle higher speed!
>>
>> It also breaks microcom-1.02.
>
> I'm pretty sure that i fixed microcom, please update and confirm
> since i only compile tested it..

My Buildroot copy is from 2007-01-16.

But why limit the UART speed?
An AT91RM9200 can do 460kBAUD.
Have several customer which would like to avoid
such artificial limitation.
Isn't it better to make the max speed a configuration item?

Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM:  +46 (706) 22 44 57
Tel:     +46  (8) 441 54 22
Fax:     +46 (8) 441 54 29
Mail: Box 2033  174 02 Sundbyberg
Visit: Kavalleriv?gen 24
          174 58 Sundbyberg'
Sweden

  reply	other threads:[~2007-01-23  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 23:32 [Buildroot] microcom broken with latest uclibc snapshot Ulf Samuelsson
2007-01-23  0:18 ` Bernhard Fischer
2007-01-23  9:06   ` Ulf Samuelsson [this message]
2007-01-23  9:49     ` Bernhard Fischer

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='004a01c73ed1$21643210$01c4af0a@atmel.com' \
    --to=ulfs@dof.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox