From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@pentafluge.infradead.org>
Subject: Re: [PATCH] sysfs support for fbdev
Date: Mon, 7 Mar 2005 13:10:04 -0500 [thread overview]
Message-ID: <9e473391050307101051d3ada3@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0503071803480.21233@pentafluge.infradead.org>
On Mon, 7 Mar 2005 18:05:35 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
> The question is will work on systems that have no space to write data.
> Alot of embedded devices can store anything. The fb.modes is very limiting
> in this case. Having a permanent RAM filesystem is expensive.
I doubt if a system that constrained needs to change modes at all. In
that case just build the mode into the driver and forget everything
else.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-07 18:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 10:00 [PATCH] sysfs support for fbdev Jon Smirl
2005-03-01 21:11 ` James Simmons
2005-03-02 18:13 ` Jon Smirl
2005-03-03 0:12 ` James Simmons
2005-03-03 0:57 ` Jon Smirl
2005-03-07 18:05 ` James Simmons
2005-03-07 18:10 ` Jon Smirl [this message]
2005-03-04 4:08 ` Jon Smirl
2005-03-04 18:26 ` James Simmons
2005-03-04 18:48 ` Jon Smirl
2005-03-04 18:50 ` Sylvain Meyer
2005-03-04 19:48 ` Buttchereit, Axel (XL)
2005-03-04 18:43 ` Sylvain Meyer
2005-03-04 18:50 ` Jon Smirl
2005-03-04 18:54 ` Sylvain Meyer
2005-03-01 23:49 ` Benjamin Herrenschmidt
2005-03-02 1:05 ` James Simmons
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=9e473391050307101051d3ada3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jsimmons@pentafluge.infradead.org \
--cc=jsimmons@www.infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).