From: Jon Smirl <jonsmirl@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Kronos <kronos@people.it>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>,
DRI Devel <dri-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] OLS and console rearchitecture
Date: Wed, 28 Jul 2004 17:23:01 -0700 (PDT) [thread overview]
Message-ID: <20040729002301.50488.qmail@web14922.mail.yahoo.com> (raw)
In-Reply-To: <1091055478.31913.7.camel@localhost.localdomain>
--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > sysfs? I sent a patch a while ago but didn't get much feedback.
>
> How do you atomically tie sysfs objects to fbdev and X permissions
> models ?
I think the plan here is for ROM export to be implemented by the PCI
driver not the video ones since other things besides video cards have
ROMs. For example some SCSI cards have a ROM so they can be boot
devices. Reading the ROM from sysfs will require root. But since all of
the hotplug events run in root context this is not a problem.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
--
next prev parent reply other threads:[~2004-07-29 0:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 18:53 OLS and console rearchitecture Jon Smirl
2004-07-28 20:10 ` Alan Cox
2004-07-28 21:31 ` Kronos
2004-07-28 22:57 ` [Linux-fbdev-devel] " Alan Cox
2004-07-29 0:23 ` Jon Smirl [this message]
2004-07-29 0:44 ` Ian Romanick
2004-07-29 1:19 ` Jon Smirl
2004-07-29 8:34 ` Geert Uytterhoeven
2004-07-30 22:19 ` Kronos
2004-07-30 23:31 ` Jon Smirl
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=20040729002301.50488.qmail@web14922.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=kronos@people.it \
--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).