Linux-Development-Sys Digest #692, Volume #8 Fri, 4 May 01 16:13:19 EDT
Contents:
Re: STLport 4.0 & g++ 2.96 (John Beardmore)
Re: Large file support on Linux? (Dragan Cvetkovic)
Re: serial port autodetection (John Beardmore)
Re: losing bottom halves ("Barry Smyth")
Re: serial port autodetection (Roberto Nibali)
Re: simple processus termination (Nate Eldredge)
Re: Hot plug PCI device (Philip Armstrong)
Re: STLport 4.0 & g++ 2.96 (Philip Armstrong)
Re: serial port autodetection (Grant Edwards)
Re: Large file support on Linux? ([EMAIL PROTECTED])
Re: serial port autodetection (Grant Edwards)
Re: Hot plug PCI device (=?iso-8859-1?Q?Andr=E9?= David)
Re: simple processus termination
Re: Just a curiosity...
Re: Large file support on Linux? (Greg Copeland)
Re: How to get a number of processors (Greg Copeland)
Re: Transfer data to mySQL Server ("D. Stimits")
Re: Large file support on Linux? (Dragan Cvetkovic)
----------------------------------------------------------------------------
From: John Beardmore <[EMAIL PROTECTED]>
Subject: Re: STLport 4.0 & g++ 2.96
Date: Fri, 4 May 2001 18:17:04 +0100
In message <[EMAIL PROTECTED]>, Steve Connet
<[EMAIL PROTECTED]> writes
>"D. Stimits" <[EMAIL PROTECTED]> writes:
>
>> Steve Connet wrote:
>> >
>> > I am trying to compile the STLport4.0 with g++ 2.96. I get to a file
>> > called money_put_w.cpp and I get the following:
>> >
>> > c++: Internal error: Segmentation fault (program cpp0)
>>
>> It isn't unusual to see an error similar to that when a template is
>> told to work with a data type that it does not know about (such as
>> because it is missing the right include file to understand that
>> type). Check to be sure that any type the template is told to use
>> has its definition available to the templates.
>
>I am getting that internal error at random places during compile of
>the STLport 4.0. I've tried many times now.
>
>Well I think it turns out gcc 2.96 was a beta compiler and never
>released, and has major problems. But Redhat [mistakenly] decided to
>put it in their RH7.0 system anyway.
>
>And like I said before, I heard it's almost next to impossible to
>revert back to an older version of gcc (ie. 2.95) on a RH7.0 system
>that has gcc 2.96 on it.
>
>So it looks like my only option here is to move forward with the beta
>GCC 3.0 branch, of which I've heard only good things so far. And since
>the GCC 3.0 beta branch has more support for the Standard C++ Library
>(ie. ostringstream & istringstream), I won't have to compile STLport
>4.0 anyway.
>
>Anyone else in the same boat as I or who have gone through a similar
>experience?
I have RH 6.2 and upgraded 2.91.66 with 2.95.3.
That fixed the problem with ostringstream and ifstream but I've not used
it much yet.
As that problem was resolved by upgrading the compiler, I didn't install
the copy of STLport that I downloaded.
I don't understand how it interacts with the two compilers that I now
have installed and don't want to break what doesn't need fixing !
If you upgrade to RH 7.1, does that get you a safe compiler ? Do you
nave any reason to stick with 7.0 ?
Cheers, J/.
--
John Beardmore
------------------------------
Subject: Re: Large file support on Linux?
From: Dragan Cvetkovic <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: 04 May 2001 13:24:08 -0400
Andreas Jaeger <[EMAIL PROTECTED]> writes:
> > The system in question is RedHat 6.2 (I think) with Linux 2.2.16,
> > glibc-2.1.3 and egcs-2.91.66
>
> Read http://www.suse.de/~aj/linux_lfs.html
>
Yes, I did read that one and found the most helpful info there. Thanks a
lot for the information provided. However, it doesn't mention RedHat 6.2 so
I just hoped RH had included some patches of their own. However, it seem
not to be the case. :-(
> You need to recompile glibc and a kernel that understands LFS.
Unfortunately this is (at this stage) not possible since this is one of
our main developers' machine that a lot of people rely on.
It seems that I will have to exclude LFS on Linux for the time being :-(
since we can't force the customers to run latest and the best Linux distro
(with kernel 2.4.x and glibc-2.2).
Thanks a lot to all answers.
Dragan
>
> Andreas
> --
> Andreas Jaeger
> SuSE Labs [EMAIL PROTECTED]
> private [EMAIL PROTECTED]
> http://www.suse.de/~aj
--
Dragan Cvetkovic,
To be or not to be is true. G. Boole
------------------------------
From: John Beardmore <[EMAIL PROTECTED]>
Subject: Re: serial port autodetection
Date: Fri, 4 May 2001 18:22:31 +0100
In message <E8BI6.22342$[EMAIL PROTECTED]>, Grant Edwards
<[EMAIL PROTECTED]> writes
> You send it a string starting with "AT" and it
>autodetects the baud rate etc. and adjusts it's settings to
>match.
But modems seem to get the baud rate set very quickly, within one or two
characters in fact.
Are they just getting lucky with the UART settings, or are they doing
something smarted along the lines of looking 'around' they UART to the
incoming wave form and working out the baud rate from the length of the
start bit or something ?
Cheers, J/.
--
John Beardmore
------------------------------
From: "Barry Smyth" <[EMAIL PROTECTED]>
Subject: Re: losing bottom halves
Date: Fri, 4 May 2001 18:40:46 +0100
Andr� David <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> > I have replaced all my code in the BH with one printk statement to show
when
> > the BH is called. I also have a printk statement in the isr directly
before
> > I add the BH to the task queue.
>
> I think I read somewhere that you shouldn't rely in printk inside
> isr's...
>
> HIH,
>
> Andre
>
> --
>
> "Share the code. If you hide it ain't good."
> Popular knowledge
The original code had no printk statements in the isr or BH and the problem
still occurred.
Barry.
------------------------------
From: Roberto Nibali <[EMAIL PROTECTED]>
Subject: Re: serial port autodetection
Date: Fri, 04 May 2001 19:49:33 +0200
> Sorry if I sounded over sarcastic -- it's been one of those
> days...
No, no sorry, it's ok. You made me recognize my mistake.
> The termios struct only tells you the current settings for the
> serial port on your end. It doesn't tell you the settings for
> the serial port on the other end of the cable.
(Slaps his forehead) -> yes, of course. Now I understand the
port autodetection he was referring to. Ok, and I have no
idea how to do this. It seems as if the people from the lirc
project did something into that direction: http://www.lirc.org/.
YMMV
> Autodetection refers to the ability to automatically detect the
> characteristics (baud, parity, etc.) of receive data and adapt
> accordingly. For example, when you hook up a serial port to
> most modern modems you don't have to set the baud rate in the
> modem. You send it a string starting with "AT" and it
> autodetects the baud rate etc. and adjusts it's settings to
> match.
Thank you for this explanation. What about my second question,
do I need to set CBAUDEX to access B115200 speed or does it
always work with 115200 baud?
Regards,
Roberto Nibali, ratz
--
mailto: `echo [EMAIL PROTECTED] | sed 's/[NOSPAM]//g'`
------------------------------
From: Nate Eldredge <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: simple processus termination
Date: 04 May 2001 10:56:53 -0700
"Peter T. Breuer" <[EMAIL PROTECTED]> writes:
> In comp.os.linux.development.system Steve Connet <[EMAIL PROTECTED]> wrote:
> > Chris <[EMAIL PROTECTED]> writes:
> > What's the difference between:
>
> > kill(pid, SIGTERM);
>
> > and
>
> > raise(SIGTERM);
>
> > Which one is preferred?
>
> They're not comparable. One sends a signal to your process. One sends a
> signal to any porcess. The man page is clear on the issue.
On the other hand, `raise(SIGNAL)' is usually implemented as
`kill(getpid(), SIGNAL)'. So if you actually want to send a signal to
yourself, it's just a matter of style. I think the name `raise' makes
it a little more obvious what's going on, but that might just be me.
--
Nate Eldredge
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Philip Armstrong)
Subject: Re: Hot plug PCI device
Date: 4 May 2001 18:28:32 +0100
In article <[EMAIL PROTECTED]>,
D. Stimits <[EMAIL PROTECTED]> wrote:
>> How can I debug the H/W of a PCI card without rebooting PC ?
>>
>I don't know the answer, but one thing is obvious...all of the registers
>and state in the PCI card is lost when you remove power, and needs to be
>reinitialized. The kernel probably has to be told to reset all of its
>ideas about this card and initialize it again. Don't ask me how you
>would do it, I just think it is the problem to be solved (perhaps the
>pci init code could be duplicated in a second program that is manually
>called).
Evil hack: compile your support for the card as a kernel module. Then
you can unload the module and remove the card, fiddle with it,
reinsert the card and reload the module to re-initialise it.
Phil
--
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt
------------------------------
From: [EMAIL PROTECTED] (Philip Armstrong)
Subject: Re: STLport 4.0 & g++ 2.96
Date: 4 May 2001 18:27:01 +0100
In article <[EMAIL PROTECTED]>,
Steve Connet <[EMAIL PROTECTED]> wrote:
>So it looks like my only option here is to move forward with the beta
>GCC 3.0 branch, of which I've heard only good things so far. And since
>the GCC 3.0 beta branch has more support for the Standard C++ Library
>(ie. ostringstream & istringstream), I won't have to compile STLport
>4.0 anyway.
These are also in gcc 2.95.3
Phil
--
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: serial port autodetection
Date: Fri, 04 May 2001 18:25:35 GMT
In article <[EMAIL PROTECTED]>, John Beardmore wrote:
>In message <E8BI6.22342$[EMAIL PROTECTED]>, Grant Edwards
><[EMAIL PROTECTED]> writes
>
>> You send it a string starting with "AT" and it
>>autodetects the baud rate etc. and adjusts it's settings to
>>match.
>
>But modems seem to get the baud rate set very quickly, within one or two
>characters in fact.
Probably on the first one.
>Are they just getting lucky with the UART settings, or are they doing
>something smarted along the lines of looking 'around' they UART to the
>incoming wave form and working out the baud rate from the length of the
>start bit or something ?
Yup. That's pretty much it.
--
Grant Edwards grante Yow! Will it improve my
at CASH FLOW?
visi.com
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Large file support on Linux?
Date: Fri, 04 May 2001 18:37:03 GMT
Dragan Cvetkovic <[EMAIL PROTECTED]> writes:
> Andreas Jaeger <[EMAIL PROTECTED]> writes:
> > > The system in question is RedHat 6.2 (I think) with Linux 2.2.16,
> > > glibc-2.1.3 and egcs-2.91.66
> >
> > Read http://www.suse.de/~aj/linux_lfs.html
> >
> Yes, I did read that one and found the most helpful info
> there. Thanks a lot for the information provided. However, it
> doesn't mention RedHat 6.2 so I just hoped RH had included some
> patches of their own. However, it seem not to be the case. :-(
Well, RH 6.2 predates LFS support having really stabilized.
> > You need to recompile glibc and a kernel that understands LFS.
> Unfortunately this is (at this stage) not possible since this is one
> of our main developers' machine that a lot of people rely on.
> It seems that I will have to exclude LFS on Linux for the time being
> :-( since we can't force the customers to run latest and the best
> Linux distro (with kernel 2.4.x and glibc-2.2).
Very Large Workspaces will have to wait until the stable public
distribution releases all support LFS.
It's unfortunate that RH 7 was so desparately noninteroperable [due to
the adoption of a Red-Hat-Only fork of GCC]; there should be little
issue a year from now.
--
(concatenate 'string "aa454" "@freenet.carleton.ca")
http://www.ntlug.org/~cbbrowne/resume.html
"Though the Chinese should adore APL, it's FORTRAN they put their
money on." -- Alan Perlis
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: serial port autodetection
Date: Fri, 04 May 2001 18:38:54 GMT
In article <[EMAIL PROTECTED]>, Roberto Nibali wrote:
>Another question: I've been writing some serial stuff too. I'm
>never sure about the CBAUDEX. Example:
>
>struct termios options;
>void set_options(void) {
> tcgetattr(fd, &options);
> options.c_cflag |= (CLOCAL | CREAD);
> options.c_cflag &= ~PARENB;
> .
> .
> .
>
> /* maybe we have to set cfsetispeed(&options, B115200 & CBAUDEX);
> * to enable higher then POSIX.1 speeds (57600 baud). See
> * cfsetiospeed(3) for further information.
> */
> cfsetispeed(&options, B115200);
> cfsetospeed(&options, B115200);
> tcsetattr(fd, TCSANOW, &options);
>}
>
>Is the CBAUDEX needed to proper address the B115200 speed?
No -- just call cfset[io]speed() with B115200 or B460800 or
whatever. The non-Posix constants already have the CBAUDEX bit
set, so the drivers know to do the right thing with the low
order 4 bits.
--
Grant Edwards grante Yow! I'm also pre-POURED
at pre-MEDITATED and
visi.com pre-RAPHAELITE!!
------------------------------
From: =?iso-8859-1?Q?Andr=E9?= David <[EMAIL PROTECTED]>
Subject: Re: Hot plug PCI device
Date: Fri, 04 May 2001 20:47:14 +0200
This is a multi-part message in MIME format.
==============579A9D96F4591F39C2CFF050
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mulder wrote:
>
> Hi,
>
> I am developing a PCI card and its Linux driver as well.
> There is a PCI protection card between PCI bus and my PCI card.
> The PCI protection card can turn my PCI card on/off when PC is ON.
>
> When PC is booted into Linux with this PCI card on,
> I can see this card's resource in /proc/pci and access it.
> To save reboot time, if I found some H/W bugs, I'd like to turn off the
> power
> to this card, removed it from the PCI protection card, fix the H/W bugs,
> re-plugget it to the PCI protection card, and turn off the power to this
> card.
> After this routine, I still can see this card's in /proc/pci.
> However, this card can't be accessed correctly now.
> All read returns 0xFFFFFFFF.
>
> How can I debug the H/W of a PCI card without rebooting PC ?
>
> Thanks!
Well, I'm also developing a PCI card that allows me to program the FPGA
through the PCI bus. Can't you do something similar?
(Of course you'll need to recofigure the board, but this way you needn't
even to touch the board, eheheh)
GLJ, ("Good Luck, Jim!")
Andre
--
"Share the code. If you hide it ain't good."
Popular knowledge
==============579A9D96F4591F39C2CFF050
Content-Type: text/x-vcard; charset=us-ascii;
name="Andre.David.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Andr� David
Content-Disposition: attachment;
filename="Andre.David.vcf"
begin:vcard
n:David;Andr�
tel;work:+41792013849
x-mozilla-html:FALSE
org:CERN - Centre Europeen de Recherche Nucleaire;Experimental Physics Division - NA60
Experiment
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
note:Geneva, Switzerland
x-mozilla-cpt:;-11552
fn:Andr� David
end:vcard
==============579A9D96F4591F39C2CFF050==
------------------------------
From: [EMAIL PROTECTED] ()
Crossposted-To: comp.os.linux.development.apps
Subject: Re: simple processus termination
Date: Fri, 04 May 2001 19:47:47 -0000
In article <[EMAIL PROTECTED]>,
Steve Connet <[EMAIL PROTECTED]> wrote:
>What's the difference between:
>
> kill(pid, SIGTERM);
>
> and
>
> raise(SIGTERM);
>
>Which one is preferred?
The raise call would kill yourself.
--
http://www.spinics.net/linux
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: Just a curiosity...
Date: Fri, 04 May 2001 19:51:59 -0000
In article <[EMAIL PROTECTED]>,
David Vidal Rodriguez <[EMAIL PROTECTED]> wrote:
>Hi out there!
>Yesterday I was "playing" the following game with my computer:
>
># echo -n "a" > foo
># cat foo | cat >> foo
># ls -l foo # (2 bytes)
># cat foo | cat >> foo
># ls -l foo # (4 bytes)
>...
>If you go on doing this (stupid) procedure, you'll get a file called foo
>with 8, 16, 32, 64, 128,... bytes, that's (still) no problem. But try it
>when foo has 32768 bytes! Instead of becoming a 64k file, the file
>system becomes full. So what's going on here exactly?
You created a race condition and find it does things a bit weird. Why
are you surprised?
--
http://www.spinics.net/linux
------------------------------
Subject: Re: Large file support on Linux?
From: Greg Copeland <[EMAIL PROTECTED]>
Date: 04 May 2001 14:55:59 -0500
Read the link that I submitted in my previous post. It specifically
mentions RH 6.2 and has links (don't know if they are still valid)
to RPMS to get you full LFS support.
Enjoy,
Greg
Dragan Cvetkovic <[EMAIL PROTECTED]> writes:
[snip]
> It seems that I will have to exclude LFS on Linux for the time being :-(
> since we can't force the customers to run latest and the best Linux distro
> (with kernel 2.4.x and glibc-2.2).
>
> Thanks a lot to all answers.
>
--
Greg Copeland, Principal Consultant
Copeland Computer Consulting
==================================================
PGP/GPG Key at http://www.keyserver.net
DE5E 6F1D 0B51 6758 A5D7 7DFE D785 A386 BD11 4FCD
==================================================
------------------------------
Crossposted-To: comp.os.linux.development.apps
Subject: Re: How to get a number of processors
From: Greg Copeland <[EMAIL PROTECTED]>
Date: 04 May 2001 14:59:29 -0500
Oddly enough, my man page for sysconf doesn't show the _SC_NPROCESSORS_CONF
option. Hmm....wonder how long it's been around. Does it exist for Linux?
Thanks,
Greg
Chris <[EMAIL PROTECTED]> writes:
> Hong Hsu wrote:
> >
> > Hi all,
> >
> > Here is my quick question. My application needs to know how many
> > processors running in the host machine, is there API which allows me to
> > get a number of processors?
>
> sysconf(2); /usr/include/bits/confname.h
>
> i.e.
>
> printf("%d\n", sysconf(_SC_NPROCESSORS_CONF));
>
> --
> Chris Lightfoot -- chris at ex dash parrot dot com -- www.ex-parrot.com/~chris/
> Sometimes I lie awake at night and ask ``Why me?'' Then a voice
> answers ``Nothing personal, your name just happened to come up.''
> (Charlie Brown, from `Peanuts', Charles Schultz)
--
Greg Copeland, Principal Consultant
Copeland Computer Consulting
==================================================
PGP/GPG Key at http://www.keyserver.net
DE5E 6F1D 0B51 6758 A5D7 7DFE D785 A386 BD11 4FCD
==================================================
------------------------------
Date: Fri, 04 May 2001 14:03:56 -0600
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.networking
Subject: Re: Transfer data to mySQL Server
Julia Donawald wrote:
>
> Hi,
> > However, I am getting this feeling that you are developing an application
> > which is purely using the DBMS as a data store while allowing a client
> program
> > to maniuplate the data.
> Yes, you are right! I want only to insert some data in a table on a mySQL
> database.
>
> >
> > If that is the case, then you will want to look at the MySQL manual and
> > interface with the database over its TCP/IP port.
> I have download the manual, but I really can't find some usefull information
> on this kind of problem.
> How will I communicate over the internet ( without ODBC ) with mySQL?
>
> Bye and thanks in advance
> Julia
If you can't use a standard communication such as ODBC, probably your
next bet is to set up an apache web server as a front end to it; via
cgi, this isn't too hard, but it is unlikely you can do it without
custom programming. A new question becomes "Exactly what applications or
protocols must have access"?
D. Stimits, [EMAIL PROTECTED]
------------------------------
Subject: Re: Large file support on Linux?
From: Dragan Cvetkovic <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: 04 May 2001 16:06:59 -0400
Greg Copeland <[EMAIL PROTECTED]> writes:
> Read the link that I submitted in my previous post. It specifically
> mentions RH 6.2 and has links (don't know if they are still valid)
> to RPMS to get you full LFS support.
>
> Enjoy,
> Greg
>
Sorry, I didn't follow the link first since I thought it just refers to
SAS' LFS-in-general page
(http://ftp.sas.com/standards/large.file/x_open.20Mar96.html). However,
after reading it this time, I realise that I still need to patch and
reinstall the kernel, which I generally don't have problems with, but which
I am not allowed to do here (since the machine is one of the main
developers' machine here).
Bye, Dragan
--
Dragan Cvetkovic,
To be or not to be is true. G. Boole
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to the
comp.os.linux.development.system newsgroup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
