On Wed, Jul 02, 2014 at 09:51:36AM +0800, Ming Lei wrote:
> On Wed, Jul 2, 2014 at 9:01 AM, Luis R. Rodriguez wrote:
> > On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
> >> At Tue, 1 Jul 2014 11:54:24 +0800,
> >> Ming Lei wrote:
> >> >
> >> > On Tue, Jul 1, 2014 at 7:30 AM, Luis R.
On Wed, Jul 2, 2014 at 9:01 AM, Luis R. Rodriguez wrote:
> On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
>> At Tue, 1 Jul 2014 11:54:24 +0800,
>> Ming Lei wrote:
>> >
>> > On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
>> > wrote:
>> > > From: "Luis R. Rodriguez"
>> > >
>> >
On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
> At Tue, 1 Jul 2014 11:54:24 +0800,
> Ming Lei wrote:
> >
> > On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
> > wrote:
> > > From: "Luis R. Rodriguez"
> > >
> > > Now that the udev firmware loader is optional request_firmware()
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
>
> On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
> wrote:
> > From: "Luis R. Rodriguez"
> >
> > Now that the udev firmware loader is optional request_firmware()
> > will not provide any information on the kernel ring buffer if
> > direct
On Tue, Jul 1, 2014 at 1:30 AM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> Now that the udev firmware loader is optional request_firmware()
> will not provide any information on the kernel ring buffer if
> direct firmware loading failed and udev firmware loading is disabled.
> If
On Tue, Jul 1, 2014 at 1:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel
On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional
On Wed, Jul 2, 2014 at 9:01 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R.
On Wed, Jul 02, 2014 at 09:51:36AM +0800, Ming Lei wrote:
On Wed, Jul 2, 2014 at 9:01 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Tue, Jul 01, 2014 at 11:22:07AM +0200, Takashi Iwai wrote:
At Tue, 1 Jul 2014 11:54:24 +0800,
Ming Lei wrote:
On Tue, Jul 1, 2014 at 7:30 AM, Luis R.
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> Now that the udev firmware loader is optional request_firmware()
> will not provide any information on the kernel ring buffer if
> direct firmware loading failed and udev firmware loading is disabled.
> If
From: "Luis R. Rodriguez"
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev firmware loading is disabled.
If no information is needed request_firmware_direct() should be used
for
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev firmware loading is disabled.
If no information is needed request_firmware_direct() should
On Tue, Jul 1, 2014 at 7:30 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
Now that the udev firmware loader is optional request_firmware()
will not provide any information on the kernel ring buffer if
direct firmware loading failed and udev
14 matches
Mail list logo