From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] drivers: console: font_: Change a glyph from "broken bar" to "vertical line"
Date: Sun, 23 Sep 2012 19:20:57 +0000 [thread overview]
Message-ID: <505F6119.4030705@gmx.de> (raw)
On 08/12/2012 03:05 PM, Bjarni Ingi Gislason wrote:
> The code 124 (0x7C, |) is rendered as a broken line in two
> fonts, instead of a continuous line. Some keyboards show a
> "broken bar" on one of theirs keys, other show a (continuous)
> "vertical line".
>
> Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Applied, as I think you're right and don't know any policy to not change
existing fonts. But it would be better if you use git to create your
patches.
Best regards,
Florian Tobias Schandinat
> ---
> linux-3.5/drivers/video/console/font_mini_4x6.c | 2 +-
> linux-3.5/drivers/video/console/font_sun8x16.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff -upr -X linux-3.5/Documentation/dontdiff linux-3.5/drivers/video/console/font_mini_4x6.c devel/linux-3.5/drivers/video/console/font_mini_4x6.c
> --- linux-3.5/drivers/video/console/font_mini_4x6.c 2012-07-21 20:58:29.000000000 +0000
> +++ devel/linux-3.5/drivers/video/console/font_mini_4x6.c 2012-08-11 15:27:41.778918653 +0000
> @@ -1092,7 +1092,7 @@ static const unsigned char fontdata_mini
> /*{*/ /* Char 124: '|' */
> 0x44, /*= [ * ] */
> 0x44, /*= [ * ] */
> - 0x00, /*= [ ] */
> + 0x44, /*= [ * ] */
> 0x44, /*= [ * ] */
> 0x44, /*= [ * ] */
> 0x00, /*= [ ] */
> diff -upr -X linux-3.5/Documentation/dontdiff linux-3.5/drivers/video/console/font_sun8x16.c devel/linux-3.5/drivers/video/console/font_sun8x16.c
> --- linux-3.5/drivers/video/console/font_sun8x16.c 2012-07-21 20:58:29.000000000 +0000
> +++ devel/linux-3.5/drivers/video/console/font_sun8x16.c 2012-08-11 15:28:22.490299722 +0000
> @@ -127,7 +127,7 @@ static const unsigned char fontdata_sun8
> /*y*/ 0x00,0x00,0x00,0x00,0x00,0xc6,0xc6,0xc6,0xc6,0xc6,0xc6,0x7e,0x06,0x0c,0xf8,0x00,
> /*z*/ 0x00,0x00,0x00,0x00,0x00,0xfe,0xcc,0x18,0x30,0x60,0xc6,0xfe,0x00,0x00,0x00,0x00,
> /*{*/ 0x00,0x00,0x0e,0x18,0x18,0x18,0x70,0x18,0x18,0x18,0x18,0x0e,0x00,0x00,0x00,0x00,
> -/*|*/ 0x00,0x00,0x18,0x18,0x18,0x18,0x00,0x18,0x18,0x18,0x18,0x18,0x00,0x00,0x00,0x00,
> +/*|*/ 0x00,0x00,0x18,0x18,0x18,0x18,0x18,0x18,0x18,0x18,0x18,0x18,0x00,0x00,0x00,0x00,
> /*}*/ 0x00,0x00,0x70,0x18,0x18,0x18,0x0e,0x18,0x18,0x18,0x18,0x70,0x00,0x00,0x00,0x00,
> /*~*/ 0x00,0x00,0x76,0xdc,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
> /* */ 0x00,0x00,0x00,0x00,0x10,0x38,0x6c,0xc6,0xc6,0xc6,0xfe,0x00,0x00,0x00,0x00,0x00,
>
next reply other threads:[~2012-09-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 19:20 Florian Tobias Schandinat [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-12 15:05 [PATCH] drivers: console: font_: Change a glyph from "broken bar" to "vertical line" Bjarni Ingi Gislason
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=505F6119.4030705@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).