Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9726] Raspberry Pi version B - Problems with UART speed in Buildroot 2016.11.2 and 2017.2
Date: Tue, 28 Mar 2017 20:34:20 +0000	[thread overview]
Message-ID: <bug-9726-163-gA2VcaPfX5@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9726-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9726

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for reporting this bug. However, this doesn't look like a Buildroot
problem, but more a U-Boot or Linux kernel problem. That being said, tons of
people are using our RPi defconfigs, and they seem to work fine, you are the
only one to report such issues.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-03-28 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 13:36 [Buildroot] [Bug 9726] New: Raspberry Pi version B - Problems with UART speed in Buildroot 2016.11.2 and 2017.2 bugzilla at busybox.net
2017-03-11 20:31 ` [Buildroot] [Bug 9726] " bugzilla at busybox.net
2017-03-11 20:38 ` bugzilla at busybox.net
2017-03-28 20:34 ` bugzilla at busybox.net [this message]
2017-03-28 20:41 ` bugzilla at busybox.net

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=bug-9726-163-gA2VcaPfX5@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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