At Thu, 31 Jan 2013 17:48:34 +0800,
Ming Lei wrote:
>
(snip)
> > +/* called from request_firmware() and request_firmware_work_func() */
> > +static int
> > +_request_firmware(const struct firmware **firmware_p, const char *name,
> > + struct device *device, bool uevent, bool nowait
On Wed, Jan 30, 2013 at 6:35 PM, Takashi Iwai wrote:
> Since 3.7 kernel, the firmware loader can read the firmware files
> directly, and the traditional user-mode helper is invoked only as a
> fallback. This seems working pretty well, and the next step would be
> to reduce the redundant user-mode
At Wed, 30 Jan 2013 19:48:15 +0800,
Ming Lei wrote:
>
> On Wed, Jan 30, 2013 at 7:08 PM, Takashi Iwai wrote:
> > At Wed, 30 Jan 2013 11:53:14 +0100,
> > Takashi Iwai wrote:
> >>
> >> At Wed, 30 Jan 2013 18:50:05 +0800,
> >> Ming Lei wrote:
> >> >
> >> > On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iw
On Wed, Jan 30, 2013 at 7:08 PM, Takashi Iwai wrote:
> At Wed, 30 Jan 2013 11:53:14 +0100,
> Takashi Iwai wrote:
>>
>> At Wed, 30 Jan 2013 18:50:05 +0800,
>> Ming Lei wrote:
>> >
>> > On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote:
>> > >
>> > > But it's supposed to be cached, no?
>> >
>> >
At Wed, 30 Jan 2013 11:53:14 +0100,
Takashi Iwai wrote:
>
> At Wed, 30 Jan 2013 18:50:05 +0800,
> Ming Lei wrote:
> >
> > On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote:
> > >
> > > But it's supposed to be cached, no?
> >
> > Generally it will be cached, but some crazy devices might come a
On Wed, Jan 30, 2013 at 6:53 PM, Takashi Iwai wrote:
> At Wed, 30 Jan 2013 18:50:05 +0800,
> Ming Lei wrote:
>>
>> On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote:
>> >
>> > But it's supposed to be cached, no?
>>
>> Generally it will be cached, but some crazy devices might come as new
>> devi
At Wed, 30 Jan 2013 18:50:05 +0800,
Ming Lei wrote:
>
> On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote:
> >
> > But it's supposed to be cached, no?
>
> Generally it will be cached, but some crazy devices might come as new
> device during resume, so we still need to handle the situation.
In
On Wed, Jan 30, 2013 at 6:31 PM, Takashi Iwai wrote:
>
> But it's supposed to be cached, no?
Generally it will be cached, but some crazy devices might come as new
device during resume, so we still need to handle the situation.
Thanks,
--
Ming Lei
--
To unsubscribe from this list: send the line "
At Wed, 30 Jan 2013 18:25:20 +0800,
Ming Lei wrote:
>
> On Wed, Jan 30, 2013 at 3:17 PM, Takashi Iwai wrote:
> >> The above usermodehelper_read_lock thing may be a functional change,
> >> and looks not what you claimed in commit log, :-). The lock is currently
> >> held in
> >> direct loading ca
On Wed, Jan 30, 2013 at 3:17 PM, Takashi Iwai wrote:
>> The above usermodehelper_read_lock thing may be a functional change,
>> and looks not what you claimed in commit log, :-). The lock is currently
>> held in
>> direct loading case, but your patch change the rule. Without holding the
>> lock,
At Wed, 30 Jan 2013 11:37:30 +0800,
Ming Lei wrote:
>
> On Tue, Jan 29, 2013 at 10:46 PM, Takashi Iwai wrote:
> > Since 3.7 kernel, the firmware loader can read the firmware files
> > directly, and the traditional user-mode helper is invoked only as a
> > fallback. This seems working pretty well
On Tue, Jan 29, 2013 at 10:46 PM, Takashi Iwai wrote:
> Since 3.7 kernel, the firmware loader can read the firmware files
> directly, and the traditional user-mode helper is invoked only as a
> fallback. This seems working pretty well, and the next step would be
> to reduce the redundant user-mod
At Tue, 29 Jan 2013 18:24:04 +0800,
Ming Lei wrote:
>
> Hi Takashi,
>
> On Sat, Jan 26, 2013 at 12:05 AM, Takashi Iwai wrote:
> > Since 3.7 kernel, the firmware loader can read the firmware files
> > directly, and the traditional user-mode helper is invoked only as a
> > fallback. This seems wo
Hi Takashi,
On Sat, Jan 26, 2013 at 12:05 AM, Takashi Iwai wrote:
> Since 3.7 kernel, the firmware loader can read the firmware files
> directly, and the traditional user-mode helper is invoked only as a
> fallback. This seems working pretty well, and the next step would be
> to reduce the redun
14 matches
Mail list logo
