All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15910] USB keyboard is not working by default "raspberrypicm4io_64_defconfig"
Date: Mon, 08 Jan 2024 13:23:00 +0000	[thread overview]
Message-ID: <bug-15910-163-zLdCHslvHp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15910-163@https.bugs.busybox.net/>

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

Benoit Pereira da Silva <benoit@mubiance.com> changed:

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

--- Comment #2 from Benoit Pereira da Silva <benoit@mubiance.com> ---
Peter, 

Thank you very much setting /dev management (Dynamic using devtmpfs + eudev)
Did solve my issue. 

I'm a newbie to buildroot, and did not know that "dev" were strictly static and
i need to activate  "devtmpfs + eudev". 

I will read attentively the documentation next time.

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

      parent reply	other threads:[~2024-01-08 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06 17:38 [Buildroot] [Bug 15910] New: USB keyboard working on Raspberry CM4 IO with "raspberrypicm4io_64_defconfig" bugzilla
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 [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=bug-15910-163-zLdCHslvHp@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 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.