From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Create an API for safely accessing BMP header fields
Date: Tue, 05 Feb 2013 09:39:41 +0200 [thread overview]
Message-ID: <5110B73D.2030405@compulab.co.il> (raw)
In-Reply-To: <511021D5.80301@myspectrum.nl>
On 02/04/13 23:02, Jeroen Hofstee wrote:
> Hello Wolfgang,
>
> On 02/04/2013 09:35 PM, Wolfgang Denk wrote:
>> Dear Nikita Kiryanov,
>>
>> In message <510FAB72.3050901@compulab.co.il> you wrote:
>>> I did mention that I consider that fix as temporary. I believe this fix
>>> is better because it addresses the issue everywhere and does so in a
>>> more maintainable way (does not require the address fix to be duplicated
>>> everywhere there is a problem).
>> Can you please explain (again) what exactly you consider the problem?
>>
>> That I can load a BMP image to anodd address, and that this will
>> result in odd results?
>>
> If you use eldk 5.3, a board will be bricked if you set the load address
> to not (an aligned address _+ 2_). So anyone who didn't know the +2
> requirement, has a bricked board (and can't recover). So this is
> really a different then md trapping, since resetting the board won't
> help... it is broken / kaput.
Agreed totally, by anyone we mean any _user_ that don't even need to care
about the bmp header structure and uses the perfectly 32 bit aligned address.
>
> That said, I am not really in favor of this solution. But I do think it needs
> to be fixed.
I actually like the approach as it gives an abstraction for:
1) different compilers and their default options,
2) architecture specific "problems" like weather it can deal with unaligned accesses
--
Regards,
Igor.
next prev parent reply other threads:[~2013-02-05 7:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 11:39 [U-Boot] [PATCH 0/5] Create an API for safely accessing BMP header fields Nikita Kiryanov
2013-02-04 11:39 ` [U-Boot] [PATCH 1/5] Add bmp_layout module for accessing BMP header data Nikita Kiryanov
2013-02-04 19:26 ` Wolfgang Denk
2013-02-04 21:26 ` Albert ARIBAUD
2013-02-04 23:11 ` Wolfgang Denk
2013-02-05 8:07 ` Igor Grinberg
2013-02-05 9:57 ` Wolfgang Denk
2013-02-05 11:38 ` Igor Grinberg
2013-02-05 13:20 ` Wolfgang Denk
2013-02-05 14:49 ` Igor Grinberg
2013-02-05 19:27 ` Wolfgang Denk
2013-02-05 6:52 ` Nikita Kiryanov
2013-02-05 9:47 ` Wolfgang Denk
2013-02-04 11:39 ` [U-Boot] [PATCH 2/5] lcd: use bmp_layout API Nikita Kiryanov
2013-02-04 11:39 ` [U-Boot] [PATCH 3/5] cmd_bmp: " Nikita Kiryanov
2013-02-04 11:39 ` [U-Boot] [PATCH 4/5] video/cfb_console: " Nikita Kiryanov
2013-02-04 11:39 ` [U-Boot] [PATCH 5/5] video/bus_vcxk: " Nikita Kiryanov
2013-02-04 11:57 ` [U-Boot] [PATCH 0/5] Create an API for safely accessing BMP header fields Albert ARIBAUD
2013-02-04 12:37 ` Nikita Kiryanov
2013-02-04 14:19 ` Albert ARIBAUD
2013-02-04 15:07 ` Nikita Kiryanov
2013-02-04 15:25 ` Albert ARIBAUD
2013-02-04 20:48 ` Wolfgang Denk
2013-02-05 7:20 ` Nikita Kiryanov
2013-02-04 20:39 ` Wolfgang Denk
2013-02-05 14:58 ` Tom Rini
2013-02-05 19:37 ` Albert ARIBAUD
2013-02-04 20:35 ` Wolfgang Denk
2013-02-04 21:02 ` Jeroen Hofstee
2013-02-05 7:39 ` Igor Grinberg [this message]
2013-02-05 6:53 ` Igor Grinberg
2013-02-05 7:22 ` Nikita Kiryanov
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=5110B73D.2030405@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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