mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: Greg KH <greg@kroah.com>, Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
	Matthew Wilcox <willy@debian.org>,
	Christoph Hellwig <hch@infradead.org>,
	Jon Smirl <jonsmirl@yahoo.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Exposing ROM's though sysfs
Date: Fri, 30 Jul 2004 13:05:57 -0700 (PDT)	[thread overview]
Message-ID: <20040730200557.30128.qmail@web14925.mail.yahoo.com> (raw)
In-Reply-To: <20040730195539.GA30466@kroah.com>

The ROMs are definitely different sizes from 2K minimum to 128KB, maybe
even larger. Varying sizes needs to be handled.

--- Greg KH <greg@kroah.com> wrote:

> On Fri, Jul 30, 2004 at 11:49:39AM -0700, Jesse Barnes wrote:
> > +
> > +	/* If the device has a ROM, map it */
> > +	if (pci_resource_len(pdev, PCI_ROM_RESOURCE)) {
> > +		pci_rom_attr.size = pci_resource_len(pdev, PCI_ROM_RESOURCE);
> > +		sysfs_create_bin_file(&pdev->dev.kobj, &pci_rom_attr);
> > +	}
> 
> Doesn't this code cause _all_ rom sizes to be the same, as you only
> have
> 1 pci_rom_attr variable?  You should create a new one for every pci
> device (making sure to clean it up when the device is removed.)
> 
> thanks,
> 
> greg k-h
> 


=====
Jon Smirl
jonsmirl@yahoo.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

  reply	other threads:[~2004-07-30 20:07 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 16:53 Jon Smirl
2004-07-30 17:10 ` Jesse Barnes
2004-07-30 17:19   ` Jesse Barnes
2004-07-30 17:24   ` Christoph Hellwig
2004-07-30 17:57     ` Jesse Barnes
2004-07-30 18:06       ` Jesse Barnes
2004-07-30 18:12       ` Matthew Wilcox
2004-07-30 18:12         ` Jesse Barnes
2004-07-30 18:20           ` Martin Mares
2004-07-30 18:49           ` Jesse Barnes
2004-07-30 19:55             ` Greg KH
2004-07-30 20:05               ` Jon Smirl [this message]
2004-07-30 20:16               ` Jesse Barnes
2004-07-30 20:29                 ` Greg KH
2004-07-30 18:59         ` Jon Smirl
2004-07-30 19:04           ` Matthew Wilcox
2004-07-30 19:30             ` Jon Smirl
2004-07-30 19:35               ` Martin Mares
2004-07-30 19:39                 ` Jon Smirl
2004-07-30 19:46                   ` Martin Mares
2004-07-30 20:03                     ` Jon Smirl
2004-07-30 20:10                       ` Martin Mares
2004-07-30 20:13                         ` Martin Mares
2004-07-30 20:25                           ` Jesse Barnes
2004-07-30 20:32                         ` Jon Smirl
2004-07-30 20:41                           ` Martin Mares
2004-07-30 20:49                             ` Jesse Barnes
2004-07-30 20:54                               ` Martin Mares
2004-07-30 21:00                                 ` Jesse Barnes
2004-07-30 21:07                               ` Jon Smirl
2004-07-30 21:12                                 ` Jesse Barnes
2004-07-30 19:47               ` Vojtech Pavlik
2004-07-30 22:18             ` Thomas Bogendoerfer
2004-07-30 22:39         ` Alan Cox
2004-07-30 19:25   ` Jon Smirl
2004-07-30 19:35     ` Vojtech Pavlik
2004-07-30 19:41       ` Jon Smirl
2004-07-30 19:48         ` Vojtech Pavlik
2004-07-30 20:20           ` Jesse Barnes
2004-07-30 22:41             ` Alan Cox
     [not found] <1091207136.2762.181.camel@rohan.arnor.net>
2004-07-30 17:24 ` Jon Smirl
2004-07-30 19:14   ` Vojtech Pavlik
2004-07-30 20:26     ` Jesse Barnes
2004-07-30 22:36       ` Alan Cox
2004-08-03 21:41         ` Benjamin Herrenschmidt
2004-08-04  0:55           ` Jesse Barnes
2004-08-04  0:59             ` Benjamin Herrenschmidt
2004-08-04  1:37               ` Jon Smirl
2004-08-04  1:57                 ` Benjamin Herrenschmidt
2004-08-04  2:16                   ` Jesse Barnes

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=20040730200557.30128.qmail@web14925.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=willy@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

all inboxes | Powered by JetHome®