Hi Andreas,
On 23 April 2017 at 04:55, Andreas Färber wrote:
> Am 19.04.2017 um 23:34 schrieb Simon Glass:
>> On 19 April 2017 at 15:06, Andreas Färber wrote:
>>> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
When iterating over the devices of an
Hi Andreas,
On 23 April 2017 at 04:48, Andreas Färber wrote:
> Am 23.04.2017 um 01:58 schrieb Simon Glass:
>> Hi,
>>
>> On 19 April 2017 at 15:34, Simon Glass wrote:
>>> On 19 April 2017 at 15:06, Andreas Färber wrote:
Am 19.04.2017
Am 19.04.2017 um 23:34 schrieb Simon Glass:
> On 19 April 2017 at 15:06, Andreas Färber wrote:
>> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
>>> When iterating over the devices of an uclass the iteration stops
>>> at the first device that cannot be probed.
>>> When
Am 23.04.2017 um 01:58 schrieb Simon Glass:
> Hi,
>
> On 19 April 2017 at 15:34, Simon Glass wrote:
>> On 19 April 2017 at 15:06, Andreas Färber wrote:
>>> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
When iterating over the devices of an uclass
On 04/23/2017 04:10 AM, Simon Glass wrote:
> Hi Heinrick,
>
> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>> When iterating over the devices of an uclass the iteration stops
>> at the first device that cannot be probed.
>> When calling booefi this will result in no
Hi Heinrick,
On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
> When iterating over the devices of an uclass the iteration stops
> at the first device that cannot be probed.
> When calling booefi this will result in no block device being
> passed to the EFI executable if
Hi,
On 19 April 2017 at 15:34, Simon Glass wrote:
> On 19 April 2017 at 15:06, Andreas Färber wrote:
>> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
>>> When iterating over the devices of an uclass the iteration stops
>>> at the first device that
On 19 April 2017 at 15:06, Andreas Färber wrote:
> Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
>> When iterating over the devices of an uclass the iteration stops
>> at the first device that cannot be probed.
>> When calling booefi this will result in no block device
On 19 April 2017 at 12:08, Heinrich Schuchardt wrote:
> On 04/19/2017 07:10 PM, Simon Glass wrote:
>> Hi Andreas,
>>
>> On 19 April 2017 at 11:00, Andreas Färber wrote:
>>> Am 19.04.2017 um 18:56 schrieb Simon Glass:
Hi Andreas,
On 19 April
Am 19.04.2017 um 13:26 schrieb Heinrich Schuchardt:
> When iterating over the devices of an uclass the iteration stops
> at the first device that cannot be probed.
> When calling booefi this will result in no block device being
"bootefi"
> passed to the EFI executable if the first device cannot
On 04/19/2017 07:10 PM, Simon Glass wrote:
> Hi Andreas,
>
> On 19 April 2017 at 11:00, Andreas Färber wrote:
>> Am 19.04.2017 um 18:56 schrieb Simon Glass:
>>> Hi Andreas,
>>>
>>> On 19 April 2017 at 10:37, Andreas Färber wrote:
Am 19.04.2017 um 17:52
Hi Andreas,
On 19 April 2017 at 11:00, Andreas Färber wrote:
> Am 19.04.2017 um 18:56 schrieb Simon Glass:
>> Hi Andreas,
>>
>> On 19 April 2017 at 10:37, Andreas Färber wrote:
>>> Am 19.04.2017 um 17:52 schrieb Simon Glass:
Hi Andreas,
On 19
Am 19.04.2017 um 18:56 schrieb Simon Glass:
> Hi Andreas,
>
> On 19 April 2017 at 10:37, Andreas Färber wrote:
>> Am 19.04.2017 um 17:52 schrieb Simon Glass:
>>> Hi Andreas,
>>>
>>> On 19 April 2017 at 09:14, Simon Glass wrote:
Hi Andreas,
On
Hi Andreas,
On 19 April 2017 at 10:37, Andreas Färber wrote:
> Am 19.04.2017 um 17:52 schrieb Simon Glass:
>> Hi Andreas,
>>
>> On 19 April 2017 at 09:14, Simon Glass wrote:
>>> Hi Andreas,
>>>
>>> On 19 April 2017 at 08:43, Andreas Färber
Am 19.04.2017 um 18:31 schrieb Álvaro Fernández Rojas:
> Hi Andreas,
>
> El 19/04/2017 a las 18:25, Andreas Färber escribió:
>> Am 19.04.2017 um 18:22 schrieb Álvaro Fernández Rojas:
>>> In case you decide to apply this version (I see you're yet deciding which
>>> is the best way to go), I
Am 19.04.2017 um 17:52 schrieb Simon Glass:
> Hi Andreas,
>
> On 19 April 2017 at 09:14, Simon Glass wrote:
>> Hi Andreas,
>>
>> On 19 April 2017 at 08:43, Andreas Färber wrote:
>>> Hi Simon,
>>>
>>> Am 19.04.2017 um 16:28 schrieb Simon Glass:
On 19
Hi Andreas,
El 19/04/2017 a las 18:25, Andreas Färber escribió:
> Am 19.04.2017 um 18:22 schrieb Álvaro Fernández Rojas:
>> In case you decide to apply this version (I see you're yet deciding which is
>> the best way to go), I tested it and it solves my problem with sysreset not
>> bein probed
Am 19.04.2017 um 18:22 schrieb Álvaro Fernández Rojas:
> In case you decide to apply this version (I see you're yet deciding which is
> the best way to go), I tested it and it solves my problem with sysreset not
> bein probed correctly.
Can you point us to which call site that is in your case
In case you decide to apply this version (I see you're yet deciding which is
the best way to go), I tested it and it solves my problem with sysreset not
bein probed correctly.
So,
Tested-by: Álvaro Fernández Rojas
El 19/04/2017 a las 13:26, Heinrich Schuchardt escribió:
>
Hi Heinrih,
On 19 April 2017 at 09:55, Heinrich Schuchardt wrote:
> On 04/19/2017 04:28 PM, Simon Glass wrote:
>> Hi Heinrich,
>>
>> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>>> When iterating over the devices of an uclass the iteration stops
On 04/19/2017 04:28 PM, Simon Glass wrote:
> Hi Heinrich,
>
> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>> When iterating over the devices of an uclass the iteration stops
>> at the first device that cannot be probed.
>> When calling booefi this will result in no
Hi Andreas,
On 19 April 2017 at 09:14, Simon Glass wrote:
> Hi Andreas,
>
> On 19 April 2017 at 08:43, Andreas Färber wrote:
>> Hi Simon,
>>
>> Am 19.04.2017 um 16:28 schrieb Simon Glass:
>>> On 19 April 2017 at 05:26, Heinrich Schuchardt
Hi Andreas,
On 19 April 2017 at 08:43, Andreas Färber wrote:
> Hi Simon,
>
> Am 19.04.2017 um 16:28 schrieb Simon Glass:
>> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>>> When iterating over the devices of an uclass the iteration stops
>>> at the
Hi Simon,
Am 19.04.2017 um 16:28 schrieb Simon Glass:
> On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
>> When iterating over the devices of an uclass the iteration stops
>> at the first device that cannot be probed.
>> When calling booefi this will result in no block
Hi Heinrich,
On 19 April 2017 at 05:26, Heinrich Schuchardt wrote:
> When iterating over the devices of an uclass the iteration stops
> at the first device that cannot be probed.
> When calling booefi this will result in no block device being
> passed to the EFI executable if
When iterating over the devices of an uclass the iteration stops
at the first device that cannot be probed.
When calling booefi this will result in no block device being
passed to the EFI executable if the first device cannot be probed.
The problem was reported by Andreas Färber in
26 matches
Mail list logo