From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15910] New: USB keyboard working on Raspberry CM4 IO with "raspberrypicm4io_64_defconfig"
Date: Sat, 06 Jan 2024 17:38:21 +0000 [thread overview]
Message-ID: <bug-15910-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15910
Bug ID: 15910
Summary: USB keyboard working on Raspberry CM4 IO with
"raspberrypicm4io_64_defconfig"
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: benoit@mubiance.com
CC: buildroot@uclibc.org
Target Milestone: ---
I use the last : Buildroot 2023.11-512-gd1c067e01b.
Without changing any options in "make menuconfig" excepted setting a root
password
1. "make raspberrypicm4io_64_defconfig"
2. "make"
3. install on a Compute module 4 with its standard IO board.
4. I always boot with a screen + i ve tested various USB keyboard.
The log are correct, some usb device are detected.
I m stuck on the prompt: "buildroot login: _"
Nothing Happens in the TTY when i press keys.
Note that the generated config.txt contains :
# enable dwc2 USB controller (USB 2.0)
dtoverlay=dwc2,dr_mode=host
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-01-06 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 17:38 bugzilla [this message]
2024-01-07 11:42 ` [Buildroot] [Bug 15910] USB keyboard is not working by default "raspberrypicm4io_64_defconfig" bugzilla
2024-01-07 19:59 ` bugzilla
2024-01-08 13:23 ` bugzilla
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-15910-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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