mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Samir Gadkari <Samir.Gadkari@atheros.com>,
	Vikram Kandukuri <Vikram.Kandukuri@atheros.com>
Subject: Where to report firmware bugs
Date: Mon, 23 Nov 2009 09:41:56 -0800	[thread overview]
Message-ID: <43e72e890911230941m29394bcapcff95de9391637a3@mail.gmail.com> (raw)

We now have open firmware for at least one wireless device upstream,
the ar9170 device firmware [1]. Granted no specific point releases
have been made yet but it should be possible in the future to do so.
I'd also like to see more open firmware in the future. I also just
reviewed some simple driver for our bluetooth devices, the ath3k
driver and it seems clear to me in these cases that firmware will do
everything and chances are the actual driver won't have much bugs.

So -- for the cases of open firmware, or in cases where we have
firmware where it does most of the job of supporting the device where
should we send users to report bugs to? The kernel bugzilla at least
does not seem to have a section for firmware? Should it?

In the case of iwl3945 it seems users report bugs directly on the
kernel.org and refer the driver directly, we'll follow that for now,
but for cases where the firmware *is* the issue it would seem easier
to be able to search for issues specifically for firmware.

Thoughts?

[1] http://wireless.kernel.org/en/users/Drivers/ar9170.fw
[2] http://bugzilla.kernel.org/show_bug.cgi?id=13799

  Luis

             reply	other threads:[~2009-11-23 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 17:41 Luis R. Rodriguez [this message]
2009-11-24  9:04 ` David Woodhouse

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=43e72e890911230941m29394bcapcff95de9391637a3@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=Samir.Gadkari@atheros.com \
    --cc=Vikram.Kandukuri@atheros.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.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

all inboxes | Powered by JetHome®