All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] microcom broken with latest uclibc snapshot.
Date: Tue, 23 Jan 2007 10:49:00 +0100	[thread overview]
Message-ID: <20070123094900.GA14123@aon.at> (raw)
In-Reply-To: <004a01c73ed1$21643210$01c4af0a@atmel.com>

On Tue, Jan 23, 2007 at 10:06:16AM +0100, Ulf Samuelsson wrote:
>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.

today is something like 2007-01-23 (for me) ;)

$ svn log -r "{2007-01-16}:HEAD" | grep -e ^r[[:digit:]] | wc -l
78

We had 78 patches going in since then.

>
>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?

I don't see a reason why it shouldn't be configurable, agree.
Perhaps send a proposed patch along the rational to the uClibc list..

      reply	other threads:[~2007-01-23  9:49 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
2007-01-23  9:49     ` Bernhard Fischer [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=20070123094900.GA14123@aon.at \
    --to=rep.dot.nop@gmail.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.