From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Patrick Boettcher <patrick.boettcher@desy.de>
Cc: Adrian Bunk <bunk@kernel.org>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] DVB: BANDWIDTH_TO_KHZ strangeness
Date: Mon, 22 Oct 2007 16:29:36 -0200 [thread overview]
Message-ID: <1193077776.15350.22.camel@gaivota> (raw)
In-Reply-To: <Pine.LNX.4.64.0710221657450.21323@pub1.ifh.de>
> I know that in the future the linux-dvb-API will also support other
> bandwidths so I'm begging for mercy for those 3 things here to not get too
> much out-of-sync with our internal code.
I don't see much problem on keeping this for a while.
However, if not causing to much troubles for you to manage, I would to
this, instead:
#if 0
/* Currently, DVB API allows only bandwidths starting from 5 GHz */
factor = BANDWIDTH_TO_KHZ(ch->u.ofdm.bandwidth);
if (factor >= 5000)
factor = 1;
else
factor = 6;
#else
factor = 6;
#endif
With the above code, gentree.pl scripts will automatically remove the
dead code from the Kernel, while keeping it defined at the development
environment.
If you want, you may also replace the #if 0 by something like:
#ifdef API_SUPPORTS_LOW_BANDWIDTH
In this case, by adding API_SUPPORTS_LOW_BANDWIDTH to gentree.pl, the
same effect of eliminating the dead code from kernel can be produced,
since gentree.pl is capable of evaluating cpp macros like the above to 0
(or 1) for the constants declared on a table inside its code.
--
Cheers,
Mauro
next prev parent reply other threads:[~2007-10-22 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 17:50 Adrian Bunk
2007-10-22 15:10 ` [v4l-dvb-maintainer] " Patrick Boettcher
2007-10-22 18:29 ` Mauro Carvalho Chehab [this message]
2007-10-22 19:54 ` Adrian Bunk
2007-10-22 20:02 ` Mauro Carvalho Chehab
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=1193077776.15350.22.camel@gaivota \
--to=mchehab@infradead.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.boettcher@desy.de \
--cc=v4l-dvb-maintainer@linuxtv.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
all inboxes | Powered by JetHome®