From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91319] Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree
Date: Fri, 01 Dec 2017 13:21:08 +0000 [thread overview]
Message-ID: <bug-91319-8800-Exhce64epp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91319-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91319
--- Comment #17 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to reeskm from comment #16)
> I'm having this exact same problem on kernel 4.9.49 on ppc 32-bit.
> I see that this was previously fixed. Should this be re-opened or should I
> file a new bug report?
When in doubt, file a new bug report. When not in doubt, file a new bug report.
Reports are trivial to merge but impossible to tease apart.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1525 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2017-12-01 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 0:34 [Bug 91319] New: Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-91319-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-13 0:41 ` [Bug 91319] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-13 9:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-13 14:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-02 7:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 3:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 5:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-06 10:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-07 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 6:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-01 4:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-01 13:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [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-91319-8800-Exhce64epp@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.