From: Anatolij Gustschin <agust@denx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: "ls > /dev/fb0" generates weird ioctls if panning is set
Date: Fri, 16 Dec 2011 23:03:02 +0000 [thread overview]
Message-ID: <20111217000302.48e92bd9@wker> (raw)
In-Reply-To: <4EEBBCEA.9020104@freescale.com>
On Fri, 16 Dec 2011 16:31:22 -0600
Timur Tabi <timur@freescale.com> wrote:
> Timur Tabi wrote:
>
> > graphics fb0: unknown ioctl command (0x402C7413)
> > graphics fb0: dir=2 type='t' (74) nr\x19 sizeD
> > graphics fb0: unknown ioctl command (0x40087468)
> > graphics fb0: dir=2 type='t' (74) nr\x104 size=8
> > graphics fb0: unknown ioctl command (0x402C7413)
> > graphics fb0: dir=2 type='t' (74) nr\x19 sizeD
>
> I figured it out. These ioctls are:
>
> #define TCGETS _IOR('t', 19, struct termios)
> #define TIOCGWINSZ _IOR('t', 104, struct winsize)
>
> I'm guessing that since I redirect stdout to /dev/fb0, Linux is
> treating /dev/fb0 as a terminal, and therefore it's receiving
> terminal ioctls.
>
> Is this something that fbdev should be supporting, or am I wrong
> to use /dev/fb0 as a terminal?
No. Do not redirect to /dev/fb0, use /dev/tty1 instead.
Anatolij
prev parent reply other threads:[~2011-12-16 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 21:49 "ls > /dev/fb0" generates weird ioctls if panning is set Timur Tabi
2011-12-16 22:31 ` Timur Tabi
2011-12-16 23:03 ` Anatolij Gustschin [this message]
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=20111217000302.48e92bd9@wker \
--to=agust@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.