Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Borton <security@conwin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Device creation
Date: Thu, 7 Apr 2011 16:34:51 -0500	[thread overview]
Message-ID: <20110407163451.6c00433c@snot.conwin.com> (raw)
In-Reply-To: <91E60E2EFEE04B0399DD86344DDEF380@VOSTROSYS>

On Thu, 7 Apr 2011 13:23:32 -0400
"Marc Leclerc" <marc-leclerc@signaturealpha.com> wrote:
> Hi, I am trying to get linuxpps working on my board using ntp. there are 
> steps described at 
> http://wiki.enneenne.com/index.php/LinuxPPS_installation which says to 
> use ldattach to assign the pps signal but so it seem I do not have 
> ldattach on my buildroot system and tryin to compile util-linux led to 
> compilation errors. Just wondering if anyone here has the know how to 
> get my /dev/pps0 created and assigned to my /dev/ttyS1. the steps also
> mentions using udev to get the /dev/pps0 created, i have tried installing and
> using it and it just messed up my other links
> 
> Best regards

/dev/pps0 is it's own device.  Look in /sysfs/class/pps/pps0/dev (you did build
support into your kernel, correct?) for the details and use mknod to create it:

mknod -m 0664 /dev/pps0 c 252 0


If you are trying to bring up ntpd with the generic NMEA driver you will
need to make a couple links to your ttyS1 and pps0:

ln -s /dev/ttyS1 /dev/gps0
ln -s /dev/pps0 /dev/gpspps0

/dev/gps0 (ttyS1) has your nmea stream.
/dev/gpspps0 (pps0) has your pps.

-Bill

  reply	other threads:[~2011-04-07 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 17:23 [Buildroot] Device creation Marc Leclerc
2011-04-07 21:34 ` Bill Borton [this message]
2011-04-08 20:33   ` Marc Leclerc
2011-04-08 21:56     ` Bill Borton
2011-04-13 21:14       ` Marc Leclerc
2011-04-14 14:55         ` Bill Borton

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=20110407163451.6c00433c@snot.conwin.com \
    --to=security@conwin.com \
    --cc=buildroot@busybox.net \
    /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