linux-kernel - Re: qcserial comes up in unhelpful custom mode?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090403150301.GA25846@suse.de>
Date:	Fri, 3 Apr 2009 08:03:01 -0700
From:	Greg KH <gregkh@...e.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: qcserial comes up in unhelpful custom mode?

On Fri, Apr 03, 2009 at 02:57:19PM +0100, Matthew Garrett wrote:
> On Thu, Apr 02, 2009 at 07:56:54PM -0700, Greg KH wrote:
> 
> > But, I have heard reports of people dual-booting with other operating
> > systems and then successfully using the device under Linux with the
> > qcserial driver, so that is one solution for some users.
> 
> So it's a driver that's useless without a closed source firmware loader, 
> either in the form of a Linux userspace application that can't be 
> distributed or in the form of Windows?

Hm, I originally thought that as well, but I have a laptop here that
doesn't seem to need the firmware code at all (I deleted it and rebooted
from poweroff and everything worked fine.)

So it seems it depends on the hardware platform.

> I thought we'd decided that drivers weren't going to be merged in that
> case (poulsbow, the original 3945 driver)

We have lots of drivers that rely on firmware that is not in the kernel
to work properly, I see this as just the same thing.

And again, I have been assured that the code is going to be distributed
soon, and that others are already using the driver successfully.

I understand your frustration, sorry.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/