Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #1662 > unrolled thread

plip: StdOut > ttyS0 & ttyS1 > StdOut

Back to article view | Back to comp.os.linux.hardware

Contents

  plip: StdOut > ttyS0 & ttyS1 > StdOut Avoid9Pdf@gmail.com - 2013-04-02 14:36 +0000
    Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-02 15:12 +0000
      Re: Kernel console output on the serial port for headless rPi Avoid9Pdf@gmail.com - 2013-04-03 05:35 +0000
        Re: Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-03 12:04 +0000
          Re: Kernel console output on the serial port for headless rPi Unknown <dog@gmail.com> - 2013-04-03 17:56 +0000
            Re: Kernel console output on the serial port for headless rPi Gordon Henderson <gordon+usenet@drogon.net> - 2013-04-03 18:11 +0000
            Re: Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-03 20:28 +0000
              Re: Kernel console output on the serial port for headless rPi Michael Black <et472@ncf.ca> - 2013-04-03 23:27 -0400
                Re: Kernel console output on the serial port for headless rPi Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-03 21:35 -0700
                  Re: Kernel console output on the serial port for headless rPi Jerry Peters <jerry@example.invalid> - 2013-04-04 20:15 +0000
                Re: Kernel console output on the serial port for headless rPi Walter Bushell <proto@panix.com> - 2013-04-04 08:36 -0400
                  Re: Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-04 13:59 +0000
                    Re: Kernel console output on the serial port for headless rPi Unknown <dog@gmail.com> - 2013-04-05 07:53 +0000
                      Re: Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-05 15:50 +0000
                        Re: Kernel console output on the serial port for headless rPi Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-05 09:17 -0700
                        Re: Kernel console output on the serial port for headless rPi Unknown <dog@gmail.com> - 2013-04-05 18:38 +0000
                          Re: Kernel console output on the serial port for headless rPi The Natural Philosopher <tnp@invalid.invalid> - 2013-04-05 19:57 +0100
                            Re: Kernel console output on the serial port for headless rPi "Nick B." <nick@replytoisnot.invalid> - 2013-04-05 22:12 +0000
                          Re: Kernel console output on the serial port for headless rPi J G Miller <miller@yoyo.ORG> - 2013-04-05 21:24 +0000
    Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-02 13:43 -0400
      Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Avoid9Pdf@gmail.com - 2013-04-03 05:35 +0000
        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-02 23:02 -0700
          Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Unknown <dog@gmail.com> - 2013-04-04 06:41 +0000
            Re: plip: StdOut > ttyS0 & ttyS1 > StdOut J G Miller <miller@yoyo.ORG> - 2013-04-04 11:53 +0000
              Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2013-04-04 08:20 -0700
              Re: plip: StdOut > ttyS0 & ttyS1 > StdOut JEDIDIAH <jedi@nomad.mishnet> - 2013-04-04 11:08 -0500
                Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-04 09:45 -0700
                  Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-04 13:43 -0400
                  Re: plip: StdOut > ttyS0 & ttyS1 > StdOut JEDIDIAH <jedi@nomad.mishnet> - 2013-04-04 14:43 -0500
                    Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-04 13:43 -0700
                      Re: plip: StdOut > ttyS0 & ttyS1 > StdOut JEDIDIAH <jedi@nomad.mishnet> - 2013-04-04 16:28 -0500
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2013-04-04 16:03 -0700
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-04 21:15 -0400
        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Dave Higton <dave@davehigton.me.uk> - 2013-04-03 21:23 +0100
          Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Unknown <dog@gmail.com> - 2013-04-04 08:57 +0000
            Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Theo Markettos <theom+news@chiark.greenend.org.uk> - 2013-04-04 22:34 +0100
              Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-04 21:17 -0400
                Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Hils <hils@saynotospam.net> - 2013-04-06 13:17 +0100
                  Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Nick Odell <gurzhfvp.jbexfubc@ntlworld.com.invalid> - 2013-04-06 14:01 +0100
                    Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Hils <hils@saynotospam.net> - 2013-04-06 15:42 +0100
                    Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Gordon Henderson <gordon+usenet@drogon.net> - 2013-04-06 15:31 +0000
                      Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-06 11:51 -0400
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut The Natural Philosopher <tnp@invalid.invalid> - 2013-04-06 17:08 +0100
                          Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Folderol <folderol@ukfsn.org> - 2013-04-06 17:27 +0100
                          Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Aragorn <stryder@telenet.be.invalid> - 2013-04-06 18:28 +0200
                            Re: plip: StdOut > ttyS0 & ttyS1 > StdOut The Natural Philosopher <tnp@invalid.invalid> - 2013-04-06 19:54 +0100
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Gordon Henderson <gordon+usenet@drogon.net> - 2013-04-06 17:07 +0000
                          Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Hils <hils@saynotospam.net> - 2013-04-06 18:54 +0100
                    Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Chris Baird <abuse@brushtail.apana.org.au> - 2013-04-07 06:10 +1000
                      Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Folderol <folderol@ukfsn.org> - 2013-04-06 22:11 +0100
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Chris Baird <abuse@brushtail.apana.org.au> - 2013-04-07 18:01 +1000
                      Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Michael Black <et472@ncf.ca> - 2013-04-06 20:23 -0400
                        Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Unknown <dog@gmail.com> - 2013-04-07 16:42 +0000
              Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Unknown <dog@gmail.com> - 2013-04-05 06:18 +0000
            Re: plip: StdOut > ttyS0 & ttyS1 > StdOut Paul <paul@pcserviceselectronics.co.uk> - 2013-04-05 13:38 +0100

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#1667

In article <alpine.LNX.2.02.1304021335180.30100@darkstar.example.org>, Michael Black <et472@ncf.ca> wrote: 

> On Tue, 2 Apr 2013, Avoid9Pdf@gmail.com wrote:
> 
> > The rPi credit-card-sized ARMbased computer which is
> > already widely distributed, has no facilites to drive VGA.
> >
> Take note that comp.sys.raspberry-pi has been approved, the creation 
> message has probably gone out by now.

Let's see if this cross-post gets there. 
> > It has however a GPIO port [?IEE488].
> > A driver for RS232 would be easy to drive the GPIO port.
> > I think plip is even simpler, and there's linux info for it.

It's IEEE488
> >
> If it's doing conversion to serial in software, then that may slow things 
> down.  THey need specific timing, which then locks out other multitasking, 
> unless things have changed from the days of Microware OS-9.  That may or 
> may not be an issue.
> 
Hardware speed is not an issue. My effort is.

> > Would it be viable to:- >
> >  connect the rPi's port to a PC's RS232-port,
> >  rPi redirect StdOut to ttyS0,
> >  PC redirect ttyS0 to StdOut ?
> >
> You set up a console that is using the RS232 port rather than  the built 
> in console.  This is easy since long before Linux came along, Unix often 
> operated this way.  Inittab is where this is done.
> 
/etc/inittab
...
# These are the standard console login getties in multiuser mode:
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
...
# Local serial lines:
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100

>     Michael
> 
>   > This would allow one Terminal of the LinuxPC to show
> > the rPi's output -- hopefully.
> >
> > I've got a crossover-cable RS232 to RS232.
> > Could I test the concept on a PC which has 2 RS232 ports,
> > with one port simulating the rPi?

Especially when hardware is envolved, the common method:
Doa, DoB, DoC...and it should fly;
is inferior to the method of:
 confirm the 1st stage [power LED];
 confirm 2nd stage
 ...
 confirm Nth stage 
 
 PS. what are the steps to send 8 'postponed' emails from
 alpine, FAST, once you've paid-to-go-online?

[toc] | [prev] | [next] | [standalone]

#1668

["Followup-To:" header set to comp.os.linux.hardware.]

On 2013-04-03, Avoid9Pdf@gmail.com <Avoid9Pdf@gmail.com> wrote:
> 
> Hardware speed is not an issue. My effort is.

If your effort is truly the issue, find a display that supports DVI or
HDMI and hook it up to the Pi as Michael suggested.  Only a fool or a
troll would think that trying to get the Pi to do plip is less effort.

--keith


-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#1679

On Tue, 02 Apr 2013 23:02:46 -0700, Keith Keller wrote:

> ["Followup-To:" header set to comp.os.linux.hardware.]
> 
> On 2013-04-03, Avoid9Pdf@gmail.com <Avoid9Pdf@gmail.com> wrote:
>> 
>> Hardware speed is not an issue. My effort is.
> 
> If your effort is truly the issue, find a display that supports DVI or
> HDMI and hook it up to the Pi as Michael suggested.  Only a fool or a
> troll would think that trying to get the Pi to do plip is less effort.
> 
> --keith

See if you can understand these 2 points:
1. you don't know the OP's environment.
  Whereas you may be located in California, the OP may be located in
  jail or somewhere where no 'display that supports DVI' is available.

2. consider the TOTAL 'effort' to develop the rPi [or any mass supplied
   product] compared to the marginal/incremental cost.
   Ie. IF the 'plip idea' is viable, countless users who have PC's, could
   have the rPi lying on the table next to their PC, and have access
   to the rPi's workings.  OK, the keybrd needs 'space' too. No I don't
   want to investigate etho.

Your mommy may want to visit that shop that you think is stupid, because
you don't know how it fits in with the rest of HER activities.
 Get it?
We don't all follow the FB/twitter herd.

[toc] | [prev] | [next] | [standalone]

#1681

On Thursday, April 4th, 2013, at 06:41:16h +0000, Chris Glur wrote:

>   Whereas you may be located in California, the OP may be located in
>   jail or somewhere where no 'display that supports DVI' is available.

Do they allow prisoners to have microcomputers in jail now?

If a video terminal does not support DVI, it will probably be
nearing the end of its life by now. 

Cathode Ray Tube display devices do not last for ever when used
on a regular basis.

> 2. consider the TOTAL 'effort' to develop the rPi [or any mass supplied
>    product] compared to the marginal/incremental cost.

That consideration is irrelevant.

>    Ie. IF the 'plip idea' is viable, countless users who have PC's, could
>    have the rPi lying on the table next to their PC, and have access
>    to the rPi's workings.

Countless users who have PCs (note there is no apostrophe because it
is not the possessive form) already have access to their rPi via
the ethernet socket or the serial port.

Incidentally, people who are buying rPis should really consider 
the much better alternatives which are available, eg the gooseberry
board or the latest, finally with gigabit ethernet,

 <http://liliputing.COM/2013/04/99-mars-board-dev-board-features-freescale-i-mx6-dual-processor.html>

Even better would be to wait for A15 boards to become readily available,
or even the really powerful A57 boards to arrive.

> No I don't want to investigate etho.

Because it is too simple and you only want to embark on
stupid and impractical notions?

> We don't all follow the FB/twitter herd.

The AWB do, but its just not the same without Eugene
(voted No. 25 in SABC3's Great South Africans), is it?

[toc] | [prev] | [next] | [standalone]

#1684

On 04/04/2013 04:53 AM, J G Miller wrote:
> On Thursday, April 4th, 2013, at 06:41:16h +0000, Chris Glur wrote:
>
>>    Whereas you may be located in California, the OP may be located in
>>    jail or somewhere where no 'display that supports DVI' is available.
>
> Do they allow prisoners to have microcomputers in jail now?

	They hire out the prisoners services and time to
various groups doing phone and computer work.  Sometimes
the employed prisoners are con men which works out in them
being able to be doing crime while doing time.

	Snip of discussion

	bliss

[toc] | [prev] | [next] | [standalone]

#1685

On 2013-04-04, J G Miller <miller@yoyo.ORG> wrote:
> On Thursday, April 4th, 2013, at 06:41:16h +0000, Chris Glur wrote:
>
>>   Whereas you may be located in California, the OP may be located in
>>   jail or somewhere where no 'display that supports DVI' is available.
>
> Do they allow prisoners to have microcomputers in jail now?
>
> If a video terminal does not support DVI, it will probably be
> nearing the end of its life by now. 

   In the corporate world you can never tell. You don't even need
to bring up the prison population here. There are plenty of cheap
people out there. Some of them even run companies. You have no 
idea what kind of resource constraints people might be working with.

   This is especially true when you are talking about a $25 bit of
hardware.

[deletia]

[toc] | [prev] | [next] | [standalone]

#1686

On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>
>    In the corporate world you can never tell. You don't even need
> to bring up the prison population here. There are plenty of cheap
> people out there. Some of them even run companies. You have no 
> idea what kind of resource constraints people might be working with.
>
>    This is especially true when you are talking about a $25 bit of
> hardware.

I know public schools in the US who are disposing of old DVI-capable
displays.  If the Original Troll can't acquire a DVI display for gratis
or dirt cheap he's got bigger problems than getting PLIP working with a
Pi.

--keith

-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#1687

On Thu, 4 Apr 2013, Keith Keller wrote:

> On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>>
>>    In the corporate world you can never tell. You don't even need
>> to bring up the prison population here. There are plenty of cheap
>> people out there. Some of them even run companies. You have no
>> idea what kind of resource constraints people might be working with.
>>
>>    This is especially true when you are talking about a $25 bit of
>> hardware.
>
> I know public schools in the US who are disposing of old DVI-capable
> displays.  If the Original Troll can't acquire a DVI display for gratis
> or dirt cheap he's got bigger problems than getting PLIP working with a
> Pi.
>
Like I said, I'm finding quite a few LCD monitors these days, some work 
outright, some need some new capacitors in the power supplies.  I think 
they all have DVI connectors, so it sets a certain standard.

That said, if someone was using their Raspberry Pi in jail, I'm sure the 
other prisoners don't want the tv set used to display code, they want to 
watch tv.

   Michael

[toc] | [prev] | [next] | [standalone]

#1688

On 2013-04-04, Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
> On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>>
>>    In the corporate world you can never tell. You don't even need
>> to bring up the prison population here. There are plenty of cheap
>> people out there. Some of them even run companies. You have no 
>> idea what kind of resource constraints people might be working with.
>>
>>    This is especially true when you are talking about a $25 bit of
>> hardware.
>
> I know public schools in the US who are disposing of old DVI-capable

...and I know companies that are still using displays that aren't modern enough to have DVI.

That works both ways.

[deletia]

   Those (few) school districts probably light cigars with $100 bills too.

[toc] | [prev] | [next] | [standalone]

#1690

On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>
> ...and I know companies that are still using displays that aren't modern enough to have DVI.

That is of course not remotely the point.  The point is that DVI
displays are cheaply and readily available if the OP were willing to
obtain one.

--keith


-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#1691

On 2013-04-04, Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
> On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>>
>> ...and I know companies that are still using displays that aren't modern enough to have DVI.
>
> That is of course not remotely the point.  The point is that DVI

   Sure it is.

> displays are cheaply and readily available if the OP were willing to
> obtain one.

    Translation: spend more money.

    That's usually a poor response to a device that's found wanting.

[toc] | [prev] | [next] | [standalone]

#1693

On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>     Translation: spend more money.

I am sure he could get one gratis if he wanted.

>     That's usually a poor response to a device that's found wanting.

If you believe that, then you should help the OP with his issue instead
of whinging about an extremely inexpensive piece of hardware.

--keith


-- 
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[toc] | [prev] | [next] | [standalone]

#1694

On Thu, 4 Apr 2013, JEDIDIAH wrote:

> On 2013-04-04, Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
>> On 2013-04-04, JEDIDIAH <jedi@nomad.mishnet> wrote:
>>>
>>> ...and I know companies that are still using displays that aren't modern enough to have DVI.
>>
>> That is of course not remotely the point.  The point is that DVI
>
>   Sure it is.
>
>> displays are cheaply and readily available if the OP were willing to
>> obtain one.
>
>    Translation: spend more money.
>
>    That's usually a poor response to a device that's found wanting.
>
And despite its use as an embedded controller, the Pi was intended as a 
cheap way to play with programming.  Just like the Vic-20 or COmmodore 64, 
connect it to the tv set and away you go.  In some ways it is silly since 
people are tossing 1GHz computers, but for 35.00 or whatever, it is an 
interesting way to provide a place to play with programming without the 
worry of accidentally damaging a main computer.

So the Pi is designed to hook up to a tv set.  Any current tv set has 
hdmi, I got that when I bought an LCD tv set 2 years ago in anticipation 
of Canada going to DTV.  I could have bought a converter, but it had been 
30 years since the only time I bought a tv set new, and this gave me an 
LCD tv set with LED backlight.  And it gave me HDMI.

Now if all your tv sets are too old, then as I pointed out, the Pi has a 
composite tv output, which means one can connect it to that green 
monochrome monitor you have left over from the Apple II days, or that 
COmmodore monitor you got with the Amiga 500.  It won't be hi definition, 
but surely if one can't scrounge up a monitor with DVI, a tv set with 
HDMI, then you can find a tv set or monitor with composite video input.

    Michael

[toc] | [prev] | [next] | [standalone]

#1673

In message <kjgf3d$f1b$1@dont-email.me>
          Avoid9Pdf@gmail.com wrote:

> In article <alpine.LNX.2.02.1304021335180.30100@darkstar.example.org>,
> Michael Black <et472@ncf.ca> wrote: 
> 
> > On Tue, 2 Apr 2013, Avoid9Pdf@gmail.com wrote:
> > 
> > > The rPi credit-card-sized ARMbased computer which is already widely
> > > distributed, has no facilites to drive VGA.
> > > 
> > Take note that comp.sys.raspberry-pi has been approved, the creation 
> > message has probably gone out by now.
> 
> Let's see if this cross-post gets there. 
> > > It has however a GPIO port [?IEE488]. A driver for RS232 would be easy
> > > to drive the GPIO port. I think plip is even simpler, and there's linux
> > > info for it.
> 
> It's IEEE488

What?

The Raspberry Pi has some GPIO (General Purpose Input/Output) lines.
IEEE-488 is the officially standardised version of the ancient GPIB,
the General Purpose Interface Bus, which is an entirely different
thing, one you're very unlikely to need.

Dave

[toc] | [prev] | [next] | [standalone]

#1680

On Wed, 03 Apr 2013 21:23:34 +0100, Dave Higton wrote:

> In message <kjgf3d$f1b$1@dont-email.me>

>> > > It has however a GPIO port [?IEE488]. A driver for RS232 would be
>> > > easy to drive the GPIO port. I think plip is even simpler, and
>> > > there's linux info for it.
>> 
>> It's IEEE488
> 
> What?
> 
> The Raspberry Pi has some GPIO (General Purpose Input/Output) lines.
> IEEE-488 is the officially standardised version of the ancient GPIB, the
> General Purpose Interface Bus, which is an entirely different thing, one
> you're very unlikely to need.
> 
> Dave

OK, thanks. Where's the spec for this GPIO.
It'll obviously be simpler than the GPIB, which is better.
BTW Ohm's law is also ancient.

[toc] | [prev] | [next] | [standalone]

#1692

In comp.sys.raspberry-pi Unknown <dog@gmail.com> wrote:
> OK, thanks. Where's the spec for this GPIO.
> It'll obviously be simpler than the GPIB, which is better.
> BTW Ohm's law is also ancient.

'GPIO' is general purpose I/O.  It's not a specific interface, there is no
standard, it's whatever the manufacturer feels like.  That's why it's
general purpose!  Here's the Pi version:

http://elinux.org/RPi_Low-level_peripherals

Theo

[toc] | [prev] | [next] | [standalone]

#1695

On Thu, 4 Apr 2013, Theo Markettos wrote:

> In comp.sys.raspberry-pi Unknown <dog@gmail.com> wrote:
>> OK, thanks. Where's the spec for this GPIO.
>> It'll obviously be simpler than the GPIB, which is better.
>> BTW Ohm's law is also ancient.
>
> 'GPIO' is general purpose I/O.  It's not a specific interface, there is no
> standard, it's whatever the manufacturer feels like.  That's why it's
> general purpose!  Here's the Pi version:
>
> http://elinux.org/RPi_Low-level_peripherals
>
> Theo
>
And now that the newsgroup for the Pi is created, the guy who wanted it 
should seed the new newsgroup with a good FAQ, just like in the old days. 
If he wants people to tune in, then he needs to start feeding posts to it, 
of useful information, so people will actually go there and start hanging 
out.

   Michael

[toc] | [prev] | [next] | [standalone]

#1708

On 05/04/13 02:17, Michael Black wrote:
> On Thu, 4 Apr 2013, Theo Markettos wrote:
>
>> In comp.sys.raspberry-pi Unknown <dog@gmail.com> wrote:
>>> OK, thanks. Where's the spec for this GPIO.
>>> It'll obviously be simpler than the GPIB, which is better.
>>> BTW Ohm's law is also ancient.
>>
>> 'GPIO' is general purpose I/O. It's not a specific interface, there is no
>> standard, it's whatever the manufacturer feels like. That's why it's
>> general purpose! Here's the Pi version:
>>
>> http://elinux.org/RPi_Low-level_peripherals
>>
>> Theo
>>
> And now that the newsgroup for the Pi is created, the guy who wanted it
> should seed the new newsgroup with a good FAQ, just like in the old
> days. If he wants people to tune in, then he needs to start feeding
> posts to it, of useful information, so people will actually go there and
> start hanging out.

I'm not sure the need for a FAQ is as great as in the days when all this 
electronic communication were still new-fangled. Since then the www has 
growed, and folks know how to search for stuff.

Perhaps just a small FAQ.

[toc] | [prev] | [next] | [standalone]

#1709

On Sat, 06 Apr 2013 13:17:55 +0100, Hils <hils@saynotospam.net> wrote:

>On 05/04/13 02:17, Michael Black wrote:
>> On Thu, 4 Apr 2013, Theo Markettos wrote:
>>
>>> In comp.sys.raspberry-pi Unknown <dog@gmail.com> wrote:
>>>> OK, thanks. Where's the spec for this GPIO.
>>>> It'll obviously be simpler than the GPIB, which is better.
>>>> BTW Ohm's law is also ancient.
>>>
>>> 'GPIO' is general purpose I/O. It's not a specific interface, there is no
>>> standard, it's whatever the manufacturer feels like. That's why it's
>>> general purpose! Here's the Pi version:
>>>
>>> http://elinux.org/RPi_Low-level_peripherals
>>>
>>> Theo
>>>
>> And now that the newsgroup for the Pi is created, the guy who wanted it
>> should seed the new newsgroup with a good FAQ, just like in the old
>> days. If he wants people to tune in, then he needs to start feeding
>> posts to it, of useful information, so people will actually go there and
>> start hanging out.
>
>I'm not sure the need for a FAQ is as great as in the days when all this 
>electronic communication were still new-fangled. Since then the www has 
>growed, and folks know how to search for stuff.
>
>Perhaps just a small FAQ.

(from comp.sys.raspberry-pi)
It depends on how evangelical you are feeling. If the group is only
for the cognoscenti then you don't need much. If on the other hand,
you are trying to encourage people like me (I only know about the Pi
from what I've read in TheRegister) to become hands-on then there
needs to be a lot more basic stuff.

I subscribed to the new group, not because I know about the Pi but
because I want to know about it. Don't think of me as a beginner, I'm
a pre-beginner, really.

Nick

[toc] | [prev] | [next] | [standalone]

#1710

On 06/04/13 14:01, Nick Odell wrote:
> On Sat, 06 Apr 2013 13:17:55 +0100, Hils<hils@saynotospam.net>  wrote:
>
>> On 05/04/13 02:17, Michael Black wrote:
>>> On Thu, 4 Apr 2013, Theo Markettos wrote:
>>>
>>>> In comp.sys.raspberry-pi Unknown<dog@gmail.com>  wrote:
>>>>> OK, thanks. Where's the spec for this GPIO.
>>>>> It'll obviously be simpler than the GPIB, which is better.
>>>>> BTW Ohm's law is also ancient.
>>>>
>>>> 'GPIO' is general purpose I/O. It's not a specific interface, there is no
>>>> standard, it's whatever the manufacturer feels like. That's why it's
>>>> general purpose! Here's the Pi version:
>>>>
>>>> http://elinux.org/RPi_Low-level_peripherals
>>>>
>>>> Theo
>>>>
>>> And now that the newsgroup for the Pi is created, the guy who wanted it
>>> should seed the new newsgroup with a good FAQ, just like in the old
>>> days. If he wants people to tune in, then he needs to start feeding
>>> posts to it, of useful information, so people will actually go there and
>>> start hanging out.
>>
>> I'm not sure the need for a FAQ is as great as in the days when all this
>> electronic communication were still new-fangled. Since then the www has
>> growed, and folks know how to search for stuff.
>>
>> Perhaps just a small FAQ.
>
> (from comp.sys.raspberry-pi)
> It depends on how evangelical you are feeling. If the group is only
> for the cognoscenti then you don't need much. If on the other hand,
> you are trying to encourage people like me (I only know about the Pi
> from what I've read in TheRegister) to become hands-on then there
> needs to be a lot more basic stuff.
>
> I subscribed to the new group, not because I know about the Pi but
> because I want to know about it. Don't think of me as a beginner, I'm
> a pre-beginner, really.

My number one tip is get used to using the command line. Almost 
everything you can do with pointing and clicking on a GUI translates to 
command line actions anyway, so you may as well get intimate with them, 
and they have more sophisticated options than GUIs allow. GUIs certainly 
have their uses, but it's best not to become dependent on them.

Linux comes with a shell scripting language which is far more 
sophisticated than the windoze equivalent. Get acquainted with it sooner 
rather than later, it will let you do things which you need separate 
programs (or at least Perl) to do on windoze.

If you're familiar with windoze commands already, they have (usually far 
more powerful) Linux equivalents.

dir becomes ls
copy becomes cp
ren becomes mv
del becomes rm

etc

At a Linux command prompt you can get basic help by typing

<command> --help

More detailed help from

man <command>

Here's a basic, very concise introduction to Unix/Linux:

http://www.ee.surrey.ac.uk/Teaching/Unix/

and some others

http://tille.garrels.be/training/tldp/

http://www.linux.org/article/view/introduction-to-linux

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | comp.os.linux.hardware

csiph-web