> -----Original Message----- > From: kernelnewbies-bounce@xxxxxxxxxxxx > [mailto:kernelnewbies-bounce@xxxxxxxxxxxx] On Behalf Of Greg Freemyer > Sent: 25 September 2006 06:50 PM > To: Mark Currie > Cc: kernelnewbies@xxxxxxxxxxxx > Subject: Re: Redirecting stdio for sx (xmodem) > > On 9/25/06, Mark Currie <mark@xxxxxxxxxxx> wrote: > > Hi, > > > > I am trying to work out how to call an application (sx) > from my serial > > comms app. Sx is an xmodem utility which uses stdio so you have to > > re-direct it to the comms port. I can talk to my target > device through > > ttyS0 but now I want to call sx to take over sending a file to the > > target using xmodem. Do I have to use system() or is there > another way > > ? Do I somehow have to pass it my active file descriptor for ttyS0? > > > > Mark Currie > > Interesting concept of kernel you seem to have. You need to > try a userspace list. > > But before you post at least read the man entries for fork(), > dup(), and exec(). I am actually a kernel newbie. I am just trying to get the kernel and rootfs downloaded onto my target so that I can continue kernel hacking. The problem is that the bootloader xmodem support times out too quickly to use minicom with sx so I am writing my own downloader. Sorry about the user space question. Mark -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
