From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14746] Lack of management after loading
Date: Sun, 18 Sep 2022 12:03:39 +0000 [thread overview]
Message-ID: <bug-14746-163-mwyPTlG7pJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14746-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14746
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Thanks for your report, but this doesn't look like a bug. We do not expect
Buildroot to provide out of the box something that has everything working,
there is often some integration, configuration and tuning that is needed.
The fact that we don't build a Qemu image with X11 enabled is expected: we
can't provide example images for all possible use-cases. Some people want X11,
some people want Wayland/Weston, some people want no graphics, etc.
The part that is relevant however in your bug report are the X server issues
when trying to load the different drivers/modules. Could you open a bug report
that specifically describes this problem?
--
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
prev parent reply other threads:[~2022-09-18 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14746-163@https.bugs.busybox.net/>
2022-04-05 13:17 ` [Buildroot] [Bug 14746] Lack of management after loading bugzilla
2022-04-07 5:02 ` bugzilla
2022-09-18 12:03 ` 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-14746-163-mwyPTlG7pJ@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