On Mon, Feb 25, 2008 at 08:18:57PM +0100, Marcel Holtmann wrote:
> Hi Dan,
> 
> > > > I have no problem exporting a simple sysfs attribute showing if the
> > > > device is either CDMA or GSDM.  I would think with that, HAL would not
> > > > need to keep any kind of tables at all, and then the device info only
> > > > has to stay in one place.
> > > 
> > > This would be ideal. IIRC the only reason for keeping the tables was
> > > that there was no such attribute. Sounds about right Dan? 
> > 
> > Yes, that was correct.  However, we should keep the current HAL
> > specification addition for a few reasons:
> > 
> > 1) devices that are only supported by usb-serial; which includes things
> > that are not CDMA/GSM modems
> > 
> > 2) devices that are PCMCIA serial cards (which are matched only on
> > class, not the manf IDs necessarily)
> > 
> > 3) previous kernel versions that wouldn't have the magic sysfs attribute
> > 
> > It would be worth exploring how to do this; but the problem is that
> > since there are devices that support both GSM and CDMA, we'd need to
> > figure out how to deal with that vs. sysfs-one-value-per-file.  We
> > shouldn't really call them "GSM" and "CDMA" but use the standards names
> > as Marcel correctly pointed out on the HAL list.
> > 
> > Thoughts greg?  It would save us a huge .fdi file because then we could
> > simply match on the linux driver name, and do some other magic in HAL
> > itself to pull out the supported standards.
> 
> what we could do is exporting a bitmap from the kernel. However this
> should be done within a subsystem and not in a per driver approach. Only
> fixing this for USB serial devices is the wrong approach in my eyes.

It would be trivial to add this as a tty attribute, which would be the
correct place, right?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to