From: Ingo Molnar <mingo@elte•hu>
To: Jaswinder Singh <jaswinder@infradead•org>
Cc: "Rafael J. Wysocki" <rjw@sisk•pl>,
David Woodhouse <david.woodhouse@intel•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
kernel-testers@vger•kernel.org,
"Maciej W. Rozycki" <macro@linux-mips•org>
Subject: Re: linux-next: Tree for June 26
Date: Sat, 28 Jun 2008 16:51:13 +0200 [thread overview]
Message-ID: <20080628145113.GA26878@elte.hu> (raw)
In-Reply-To: <1214646863.2660.22.camel@jaswinder.satnam>
* Jaswinder Singh <jaswinder@infradead•org> wrote:
> No, firmware is same.
>
> Our Firmware blob looks like this...
> u8 firmware_major
> u8 firmware_minor
> u8 firmware_fix
> u8 pad
> __be32 start_address
> __be32 length (total, including BSS sections to be zeroed)
> data... (in __be32 words, which is native for the firmware)
>
> rest of data is same and you can see it manually.
>
> I am surprise why Ingo is using hex dump and he finds different data.
>
> And I did not received any feedback from Ingo yet.
sorry - it was just a drive-by comment i made to Rafael while i reacted
to the x86 portion of his mail - i dont have this tg3 problem myself so
there's nothing i could report or test. I only looked at the patch that
was identified and the tg3FwText[] array appeared to be different - but
as you explain it above, that is OK and the firmware image is the same.
Ingo
next prev parent reply other threads:[~2008-06-28 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 15:08 linux-next: Tree for June 26 Stephen Rothwell
[not found] ` <20080627010842.e1a0c4b5.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-26 23:38 ` Rafael J. Wysocki
[not found] ` <200806270138.53895.rjw-KKrjLPT3xs0@public.gmane.org>
2008-06-27 9:28 ` David Woodhouse
2008-06-27 10:51 ` David Woodhouse
2008-06-27 12:42 ` Kamalesh Babulal
2008-06-27 12:48 ` David Woodhouse
[not found] ` <1214563913.10393.180.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-06-27 23:04 ` Rafael J. Wysocki
2008-06-28 9:54 ` Jaswinder Singh
2008-06-28 10:32 ` David Woodhouse
[not found] ` <1214649164.10393.265.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-06-29 0:15 ` Rafael J. Wysocki
2008-06-29 8:01 ` David Woodhouse
2008-06-29 11:36 ` Rafael J. Wysocki
[not found] ` <200806291336.44603.rjw-KKrjLPT3xs0@public.gmane.org>
2008-06-29 20:49 ` David Woodhouse
2008-06-28 14:51 ` Ingo Molnar [this message]
2008-06-28 10:09 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2009-06-26 5:46 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080628145113.GA26878@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=akpm@linux-foundation$(echo .)org \
--cc=david.woodhouse@intel$(echo .)com \
--cc=jaswinder@infradead$(echo .)org \
--cc=kernel-testers@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=macro@linux-mips$(echo .)org \
--cc=rjw@sisk$(echo .)pl \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox