From: B.R. Oake <broake@openmailbox.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Mainline U-Boot, EHCI, usbkbd not working (workaround)
Date: Sun, 04 Jan 2015 21:51:49 +0000 [thread overview]
Message-ID: <54A9B5F5.7070908@openmailbox.org> (raw)
In-Reply-To: <54A98EF0.6080209@redhat.com>
On 04/01/15 19:05, Hans de Goede wrote:
> The problem is that u-boot does not allow building both ohci and
> ehci drivers into the same u-boot binary, so we cannot enable both
> usb-1 and usb-2 support at the same time.
>
> So we're stuck with having only usb-2 support until someone reworks
> u-boot's usb code, and keyboards and mice are typically usb-1 devices,
> the workaround for this is to plug in a usb-2 hub so that the board
> sees a usb-2 device, and then plug the mouse / keyboard into that
> hub.
Thanks for the explanation Hans.
At U-Boot time, the only USB device I would need is the keyboard, and
I would rather avoid adding a hub if I don't otherwise need one, so
perhaps I can build U-Boot with the OHCI driver enabled instead of EHCI?
I tried removing CONFIG_USB_EHCI and adding:
CONFIG_USB_OHCI_NEW
CONFIG_SYS_USB_OHCI_BOARD_INIT
CONFIG_SYS_USB_OHCI_CPU_INIT
CONFIG_SYS_USB_OHCI_REGS_BASE=0x01c14400
CONFIG_SYS_USB_OHCI_SLOT_NAME="sunxi_slot_0"
CONFIG_SYS_USB_OHCI_MAX_ROOT_PORTS=1
which built and ran, but gave the error "unknown command usb". Can
this approach be made to work?
Cheers,
B.R.
next prev parent reply other threads:[~2015-01-04 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2396754.FY5fnKSFZ8@x64.localnet>
2015-01-04 18:21 ` [U-Boot] [linux-sunxi] Mainline U-Boot, EHCI, usbkbd not working (workaround) B.R. Oake
2015-01-04 19:05 ` Hans de Goede
2015-01-04 21:51 ` B.R. Oake [this message]
2015-01-05 2:49 ` Simon Glass
2015-01-05 3:05 ` Marek Vasut
2015-01-05 7:10 ` Hans de Goede
2015-01-05 16:34 ` Simon Glass
2015-12-13 10:30 ` John Morelli
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=54A9B5F5.7070908@openmailbox.org \
--to=broake@openmailbox.org \
--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.