linux-kernel - Re: [PATCH 27/30] staging/vme: rework the bus model

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]

Date:	Wed, 27 Oct 2010 10:16:21 +0100
From:	Martyn Welch <martyn.welch@...com>
To:	"Emilio G. Cota" <cota@...ap.org>
CC:	Greg KH <greg@...ah.com>, LKML <linux-kernel@...r.kernel.org>,
	Juan David Gonzalez Cobas <david.cobas@...il.com>
Subject: Re: [PATCH 27/30] staging/vme: rework the bus model

On 26/10/10 02:02, Emilio G. Cota wrote:
> On Mon, Oct 25, 2010 at 12:24:38 +0100, Martyn Welch wrote:
>> On 23/10/10 00:27, Emilio G. Cota wrote:
>>>> * installing drivers even before the bridges they need are present
>>>>   seems counter-intuitive and wrong.
>>
>> There are plenty of instances where a driver can be loaded before the
>> bus is probed or a device is even present. When the bus become
>> available, the probe routine will be run.
> 
> That would be acceptable if and only if no other alternative was available.
> 
> It doesn't make any sense to constrain ourselves to installing
> drivers only BEFORE loading bridge drivers.
> 

I have no idea what your doing, but that simply isn't the case. Your
right - that really would not make any sense, however I'm happily
loading the bridge drivers before any VME device drivers here.

Martyn


-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square,
Manchester,
E martyn.welch@...com                        |   M2 3AB  VAT:GB 927559189
--
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/