On Tue, Apr 17, 2018 at 10:47 AM, Dave Young wrote:
> On 04/16/18 at 08:39pm, Bhupesh Sharma wrote:
>> Hi Dave,
>>
>> On Mon, Apr 16, 2018 at 1:43 PM, Dave Young wrote:
>> > Hi Bhupesh,
>> >
>> > On 04/03/18 at 07:28pm, Bhupesh Sharma wrote:
>> >> Hi James,
On 04/16/18 at 08:39pm, Bhupesh Sharma wrote:
> Hi Dave,
>
> On Mon, Apr 16, 2018 at 1:43 PM, Dave Young wrote:
> > Hi Bhupesh,
> >
> > On 04/03/18 at 07:28pm, Bhupesh Sharma wrote:
> >> Hi James,
> >>
> >> Sorry for the delay, I had a long weekend last week.
> >>
> >> On Tue,
Hi Dave,
On Mon, Apr 16, 2018 at 1:43 PM, Dave Young wrote:
> Hi Bhupesh,
>
> On 04/03/18 at 07:28pm, Bhupesh Sharma wrote:
>> Hi James,
>>
>> Sorry for the delay, I had a long weekend last week.
>>
>> On Tue, Mar 27, 2018 at 7:01 PM, James Morse wrote:
Hi Bhupesh,
On 04/03/18 at 07:28pm, Bhupesh Sharma wrote:
> Hi James,
>
> Sorry for the delay, I had a long weekend last week.
>
> On Tue, Mar 27, 2018 at 7:01 PM, James Morse wrote:
> > Hi Akashi, Bhupesh,
> >
> > On 27/03/18 10:04, AKASHI Takahiro wrote:
> >> On Mon, Mar
Hello,
On Tue, Apr 3, 2018 at 7:28 PM, Bhupesh Sharma wrote:
> Hi James,
>
> Sorry for the delay, I had a long weekend last week.
>
> On Tue, Mar 27, 2018 at 7:01 PM, James Morse wrote:
>> Hi Akashi, Bhupesh,
>>
>> On 27/03/18 10:04, AKASHI Takahiro
Hi James,
Sorry for the delay, I had a long weekend last week.
On Tue, Mar 27, 2018 at 7:01 PM, James Morse wrote:
> Hi Akashi, Bhupesh,
>
> On 27/03/18 10:04, AKASHI Takahiro wrote:
>> On Mon, Mar 26, 2018 at 02:29:31PM +0530, Bhupesh Sharma wrote:
>>> On Tue, Mar 20, 2018
Hi Akashi, Bhupesh,
On 27/03/18 10:04, AKASHI Takahiro wrote:
> On Mon, Mar 26, 2018 at 02:29:31PM +0530, Bhupesh Sharma wrote:
>> On Tue, Mar 20, 2018 at 12:36 AM, Bhupesh Sharma wrote:
>>> On Mon, Mar 19, 2018 at 8:15 PM, AKASHI Takahiro
>>>
On Mon, Mar 26, 2018 at 02:29:31PM +0530, Bhupesh Sharma wrote:
> Hi Akashi,
>
> On Tue, Mar 20, 2018 at 12:36 AM, Bhupesh Sharma wrote:
> > On Mon, Mar 19, 2018 at 8:15 PM, AKASHI Takahiro
> > wrote:
> >> On Mon, Mar 19, 2018 at 04:05:38PM
Hi Akashi,
On Tue, Mar 20, 2018 at 12:36 AM, Bhupesh Sharma wrote:
> On Mon, Mar 19, 2018 at 8:15 PM, AKASHI Takahiro
> wrote:
>> On Mon, Mar 19, 2018 at 04:05:38PM +0530, Bhupesh Sharma wrote:
>>> At several occasions it would be useful to dump
On Mon, Mar 19, 2018 at 8:15 PM, AKASHI Takahiro
wrote:
> On Mon, Mar 19, 2018 at 04:05:38PM +0530, Bhupesh Sharma wrote:
>> At several occasions it would be useful to dump the fdt
>> blob being passed to the second (kexec/kdump) kernel
>> when '-d' flag is specified
On Mon, Mar 19, 2018 at 04:05:38PM +0530, Bhupesh Sharma wrote:
> At several occasions it would be useful to dump the fdt
> blob being passed to the second (kexec/kdump) kernel
> when '-d' flag is specified while invoking kexec/kdump.
Why not just save binary data to a file and interpret it
with
At several occasions it would be useful to dump the fdt
blob being passed to the second (kexec/kdump) kernel
when '-d' flag is specified while invoking kexec/kdump.
This allows one to look at the device-tree fields that
is being passed to the secondary kernel and accordingly
debug issues.
This
12 matches
Mail list logo