From: Greg KH <greg@kroah.com>
To: Manuel Estrada Sainz <ranty@debian.org>
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
"'David Gibson'" <david@gibson.dropbear.id.au>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: firmware separation filesystem (fwfs)
Date: Wed, 16 Apr 2003 21:06:41 -0700 [thread overview]
Message-ID: <20030417040641.GD2201@kroah.com> (raw)
In-Reply-To: <20030417033154.GD31473@ranty.ddts.net>
On Thu, Apr 17, 2003 at 05:31:54AM +0200, Manuel Estrada Sainz wrote:
>
> I don't know that much about sysfs, after a little investigation, it
> seams like sysfs entries are restricted in size to PAGE_SIZE, which on
> i386 is 4K, and ezusb firmware is already 6.9K in size.
>
> I would really appreciate someone more knowledgeable than myself
> commenting on the possibility of extending sysfs to fill this gap.
Yes, I don't think this would be that tough to add. Matthew Wilcox
posted a patch to clean up a lot of problems with the current binary
file sysfs interface, and after that patch is in the main tree, it
shouldn't be that touch to change to support these kinds of files.
Although I do like the idea and implementation of fwfs, nice job :)
Hope this helps,
greg k-h
next prev parent reply other threads:[~2003-04-17 3:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 2:00 firmware separation filesystem (fwfs) Perez-Gonzalez, Inaky
2003-04-17 3:31 ` Manuel Estrada Sainz
2003-04-17 4:06 ` Greg KH [this message]
2003-04-17 3:48 ` 'David Gibson'
-- strict thread matches above, loose matches on Subject: below --
2003-04-17 4:07 Perez-Gonzalez, Inaky
2003-04-17 0:17 Perez-Gonzalez, Inaky
2003-04-16 0:57 Manuel Estrada Sainz
2003-04-16 11:31 ` Alan Cox
2003-04-16 14:46 ` David Gibson
2003-04-16 16:36 ` Manuel Estrada Sainz
2003-04-16 15:47 ` Alan Cox
2003-04-16 16:57 ` Riley Williams
2003-04-17 13:43 ` Alan Cox
2003-04-17 13:43 ` Alan Cox
2003-04-17 1:23 ` David Gibson
2003-04-17 13:12 ` Alan Cox
2003-04-19 20:41 ` Manuel Estrada Sainz
2003-04-19 21:52 ` Alan Cox
2003-04-20 19:26 ` Manuel Estrada Sainz
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=20030417040641.GD2201@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@gibson.dropbear.id.au \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranty@debian.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