Em Sat, 14 Dec 2013 19:47:45 +0200 Antti Palosaari <crope@xxxxxx> escreveu: > On 14.12.2013 19:05, Hans Verkuil wrote: > > On 12/14/2013 05:45 PM, Antti Palosaari wrote: > >> Hello > >> One possible problem I noticed is device node name. > >> > >> Documentation/devices.txt > >> > >> 65 block SCSI disk devices (16-31) > >> 0 = /dev/sdq 17th SCSI disk whole disk > >> 16 = /dev/sdr 18th SCSI disk whole disk > >> 32 = /dev/sds 19th SCSI disk whole disk > >> ... > >> 240 = /dev/sdaf 32nd SCSI disk whole disk > >> > >> Partitions are handled in the same way as for IDE > >> disks (see major number 3) except that the limit on > >> partitions is 15. > >> > >> > >> 81 char video4linux > >> 0 = /dev/video0 Video capture/overlay device > >> ... > >> 63 = /dev/video63 Video capture/overlay device > >> 64 = /dev/radio0 Radio device > >> ... > >> 127 = /dev/radio63 Radio device > >> 224 = /dev/vbi0 Vertical blank interrupt > >> ... > >> 255 = /dev/vbi31 Vertical blank interrupt > >> > >> > >> What I understand, /dev/sdr is not suitable node name as it conflicts > >> with existing node name. > > > > Good catch, that won't work :-) > > > >> Any ideas? > > > > /dev/sdradio? > > /dev/swradio? > > > Lets do a small poll here. Everyone, but me, has a one vote ;) I vote for swradio. The patches look ok to me, provided that you add the proper DocBook bits on each of them. I didn't like much that now have 3 ways to describe frequencies. I think we should latter think on moving the frequency conversion to the core, and use u64 with 1Hz step at the internal API, converting all the drivers to use it. IMHO, we should also provide a backward-compatible way that would allow userspace to choose to use u64 1-Hz-stepping frequencies. Of course the changes at the drivers is out of the scope, but perhaps we should not apply patch 4/7, replacing it, instead, by some patch that would move the frequency size to u64. > > regards > Antti -- Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
