All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon South <simon@simonsouth.net>
To: u-boot@lists.denx.de
Subject: Pinebook Pro keyboard (RK3399 OHCI)?
Date: Tue, 14 Jul 2020 13:18:25 -0400	[thread overview]
Message-ID: <87v9iq6mn2.fsf@simonsouth.net> (raw)
In-Reply-To: <87mu42ytfn.fsf@lechat.rtp-net.org> (Arnaud Patard's message of "Tue, 14 Jul 2020 18:04:12 +0200")

Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
> Did you check the stdin variable content if it contains only "usbkbd" ?
> If you have more than one value in it (like "serial,usbkbd"), do you have
> CONSOLE_MUX configuration setting enabled ?

Yes, "stdin" is set to "serial,usbkbd" and CONSOLE_MUX is set. The
console works fine via the serial connection, apart from being sluggish
while USB is enabled.

> Same here.

I just now tried removing another variable by building U-Boot from a
fresh checkout on the PBP itself, rather than cross-compiling from my
x86_64 machine as I normally do. Same result.

So I'm completely at a loss.

If you have them handy, would you be willing to email me (off-list) your
idbloader.img and u-boot.itb files please so I can try booting them on
my hardware? I'm starting to think at this point I somehow got a lemon,
but if your build works that would at least point to something I've
missed in my setup.

-- 
Simon South
simon at simonsouth.net

  reply	other threads:[~2020-07-14 17:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 20:31 Pinebook Pro keyboard (RK3399 OHCI)? Simon South
2020-07-14  8:07 ` Peter Robinson
2020-07-14 10:48   ` Simon South
2020-07-14 10:53     ` Peter Robinson
2020-07-14 15:05     ` Arnaud Patard
2020-07-14 15:29       ` Simon South
2020-07-14 15:40         ` Peter Robinson
2020-07-14 16:04         ` Arnaud Patard
2020-07-14 17:18           ` Simon South [this message]
2020-10-01 14:56 ` Simon South
2020-10-02  8:07   ` Arnaud Patard

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=87v9iq6mn2.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=u-boot@lists.denx.de \
    /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.