Openmoko Bug #2338: ttySAC nodes are not created automatically with devtmpfs

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Openmoko Bug #2338: ttySAC nodes are not created automatically with devtmpfs

Openmoko Public Trac
#2338: ttySAC nodes are not created automatically with devtmpfs
--------------------+-------------------------------------------------------
 Reporter:  jama    |          Owner:  openmoko-kernel
     Type:  defect  |         Status:  new            
 Priority:  normal  |      Milestone:                
Component:  kernel  |        Version:  unspecified    
 Severity:  normal  |       Keywords:                
 Haspatch:  0       |      Blockedby:                
Estimated:          |    Patchreview:                
 Blocking:          |   Reproducible:                
--------------------+-------------------------------------------------------
 They are created OK with udev or with mknod, but with devtmpfs they are
 missing completely.

 Would be nice to fix it in kernel instead of mknod in initscripts
 workaround. At least ttySAC0 is needed for GSM and ttySAC1 for GPS. There
 is also ttySAC2 used as kernel console.

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2338>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
Reply | Threaded
Open this post in threaded view
|

Re: Openmoko Bug #2338: ttySAC nodes are not created automatically with devtmpfs

Openmoko Public Trac
#2338: ttySAC nodes are not created automatically with devtmpfs
--------------------+-------------------------------------------------------
 Reporter:  jama    |          Owner:  openmoko-kernel
     Type:  defect  |         Status:  new            
 Priority:  normal  |      Milestone:                
Component:  kernel  |        Version:  unspecified    
 Severity:  normal  |       Keywords:                
 Haspatch:  0       |      Blockedby:                
Estimated:          |    Patchreview:                
 Blocking:          |   Reproducible:                
--------------------+-------------------------------------------------------

Comment(by psonek):

 They are created ok, but under different names:

 /dev/s3c2410_serial2
 /dev/s3c2410_serial1
 /dev/s3c2410_serial0

 Question is if we should fix this in kernel (patch attached) or in
 userspace.

 Kernel is better because most of existing docs on internet 36000/16000 use
 ttySAC names. Also kernel size reduces a bit (like 10 bytes? ;-)

 But if kernel patch breaks some system (maybe android?) we should fix our
 userspaces.

 You can also cherry pick this commit:
 http://github.com/radekp/linux-2.6/commit/ec52149c715232584731e36303971a25bf3d8bee

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2338#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
Reply | Threaded
Open this post in threaded view
|

Re: Openmoko Bug #2338: ttySAC nodes are not created automatically with devtmpfs

Openmoko Public Trac
In reply to this post by Openmoko Public Trac
#2338: ttySAC nodes are not created automatically with devtmpfs
--------------------+-------------------------------------------------------
 Reporter:  jama    |          Owner:  openmoko-kernel
     Type:  defect  |         Status:  new            
 Priority:  normal  |      Milestone:                
Component:  kernel  |        Version:  unspecified    
 Severity:  normal  |       Keywords:                
 Haspatch:  0       |      Blockedby:                
Estimated:          |    Patchreview:                
 Blocking:          |   Reproducible:                
--------------------+-------------------------------------------------------

Comment(by lindi):

 My userland just uses the names /dev/gps and /dev/gsm. I never understood
 why I'd need to constantly dig the source to figure out which device is
 which one :-) (It is hard to make an offline copy of the wiki and no
 manual page explains the naming).

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2338#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac