Messages in this thread |  | | | From | Jesse Barnes <> | | Subject | Re: Exposing ROM's though sysfs | | Date | Fri, 30 Jul 2004 13:25:53 -0700 |
| |
On Friday, July 30, 2004 1:13 pm, Martin Mares wrote: > > Do I understand it correctly that the ROM-in-sysfs hack is intended only > > for debugging? If it is so, I do not see why we should do anything > > complicated in order to avoid root shooting himself in the foot. > > ... for which the config space access code already sets the precedent -- > there exist (rare) devices which have configuration registers with side > effects on reads, making it possible to produce SCSI errors or even crash > the system by just dumping the config space. Even on these devices, the > kernel does not attempt to forbid reading of these registers via sysfs.
Well, this is what I initially argued with willy...
I think typical usage will be: o dri fires off hotplug event o userland card POSTing tool reads the ROM, saving it off for future use, and POSTs the card o userland tool calls back into dri saying that the card is ready o dri driver operates happily
So dealing with users accessing the rom file after a driver is up and running may not be worth the trouble.
Jesse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |