public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linux@MichaelGeng.de (Michael Geng)
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, kraxel@bytesex.org
Subject: Re: [ANNOUNCE] new driver for teletext decoder SAA5246A
Date: Wed, 25 Feb 2004 19:10:41 +0100	[thread overview]
Message-ID: <20040225181041.GA2446@t-online.de> (raw)
In-Reply-To: <20040225041330.51961b28.akpm@osdl.org>

On Wed, Feb 25, 2004 at 04:13:30AM -0800, Andrew Morton wrote:
> linux@MichaelGeng.de (Michael Geng) wrote:
> >
> > http://www.michaelgeng.de/linux/saa5246a-2.6.3.patch

Location of the updated patch:

http://www.michaelgeng.de/linux/saa5246a-rev1-2.6.3.patch

> jdelay() is odd - it's a shame it has to fiddle with signals in that
> manner.  Are you sure it's really needed?

I copied this jdelay() stuff from the existing saa5249.c 
without much reflecting about it. 

In my opinion it is up to the user space program to request the 
driver status in reasonable time intervals in order to see if a
requested videotext page has been received. The kernel driver 
should answer without delay. It can't be the task of the kernel
driver to prevent a user space program from querying the status 
10000 times a second.

Conclusion: You are right, the jdelay() stuff is not necessary
at all. I removed it completely from the code. After that I 
tested the newly compiled driver using Martin Buck's vtxget 
program. The command 

time vtxget 100

consumed about 0.4secs sys time before and about 0.5secs after
removing jdelay(). I think this is ok, the driver still works 
fine.

> Also, I suggest you try removing all those `inline' statements.  Then see
> if /usr/bin/size claims that the code shrunk.  Often it does.

No, it doesn't shrink. I already tested that when I developed 
the driver with saa5249.c as a template. Now I made a completely
inline-free version, but /usr/bin/size shows exactly the same
size. By the way, this shows that gcc does a good job. Of course
this could also depend on the architecture, but on my Pentium 4
box gcc really puts the inline parts inline.

There are 2 reason why I used these inline functions:

1. A huge ioctl() function would be more difficult to understand
   than those individual inline functions. Don't you agree?

2. Some of those inline functions are not only specific to the
   SAA5246A. They could also be used for the existing driver to
   the SAA5249 or other drivers of that series. Maybe this could 
   be useful if someone wants to write another driver or even
   in order to merge the SAA5246A and SAA5249 drivers into 1 
   driver. Maybe this is possible, I'm not sure. I would
   like to try, but unfortunately I don't have a SAA5249. Does
   anybody want to sell his sample to me?

Conclusion: I would prefer to keep all those inline functions.
The inline functions are not changed in the updated patch.
			 
> Apart from that, looks fine.  Please send me a copy via email along with a
> suitable changelog for checking into Bitkeeper and copy Gerd Knorr
> <kraxel@bytesex.org>, thanks.

If you want to add the patch, how about the following changelog:

[V4L]: Added new driver for Teletext decoder SAA5246A from Philips

Thank you very much for your help,
Michael


  parent reply	other threads:[~2004-02-25 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 11:34 [ANNOUNCE] new driver for teletext decoder SAA5246A Michael Geng
     [not found] ` <20040225041330.51961b28.akpm@osdl.org>
2004-02-25 18:10   ` Michael Geng [this message]
2004-02-25 21:36     ` Andrew Morton
2004-02-25 22:29       ` Michael Geng
     [not found] ` <403CFBD9.2000607@convergence.de>
2004-02-25 21:11   ` Michael Geng

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=20040225181041.GA2446@t-online.de \
    --to=linux@michaelgeng.de \
    --cc=akpm@osdl.org \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    /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