From: hayeswang <hayeswang@realtek.com>
To: "'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] net/r8169: update the new parser for the new firmware
Date: Fri, 17 Jun 2011 11:25:13 +0800 [thread overview]
Message-ID: <8AC7DE11560749B895F99EBA7D42AA49@realtek.com.tw> (raw)
In-Reply-To: <20110616225904.GA2064@electric-eye.fr.zoreil.com>
> -----Original Message-----
> From: Francois Romieu [mailto:romieu@fr.zoreil.com]
> Sent: Friday, June 17, 2011 6:59 AM
> To: Hayeswang
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] net/r8169: update the new parser for
> the new firmware
>
> Hayes Wang <hayeswang@realtek.com> :
> > Update the parser for the new firmware which is embedded
> some information.
>
> I have modified several things :
> - s/u32/__le32/ in fw_info
> - fix unsigned (size_t) comparisons
> - more size checks before dereferencing fw_info
>
Thanks. They are fine.
> The new firmware format should be the same. The old
> r8168d-1.fw firmware proved usable when prefixed with :
>
> 0000000: 0000 0000 3031 0000 0000 0000 0000 0000 ....01..........
> 0000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 0000020: 0000 0000 3000 0000 7501 0000 a000 0000 ....0...u.......
>
> I realized after testing that netif_err could be abused with
> non-string fw_info.version. :o/
>
Excuse me. I don't understand what you want to express. Do you mean the
situation of the old paser with the new firmware for checking the firmware? For
the normal situation, the old paser would not use the new firmware. And I put
zero in front of the new firmware to prevent the old paser from running it. That
is all I do.
If you don't mean that, I could promise the new firmware I release would contain
the valid string unless someone modifies it.
> Comments ?
>
Best Regards,
Hayes
next prev parent reply other threads:[~2011-06-17 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 3:45 [PATCH v2] net/r8169: update the new parser for the new firmware Hayes Wang
2011-06-16 22:59 ` Francois Romieu
2011-06-17 3:25 ` hayeswang [this message]
2011-06-17 6:39 ` Francois Romieu
2011-06-17 12:22 ` Ben Hutchings
2011-06-17 12:53 ` Francois Romieu
2011-06-17 14:50 ` Ben Hutchings
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=8AC7DE11560749B895F99EBA7D42AA49@realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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