From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: dvb_usb_v2: use pointers to properties[REGRESSION]
Date: Sat, 16 Jun 2012 01:54:46 +0300 [thread overview]
Message-ID: <4FDBBD36.9020302@iki.fi> (raw)
In-Reply-To: <1339798273.12274.21.camel@Route3278>
Hello Malcolm,
On 06/16/2012 01:11 AM, Malcolm Priestley wrote:
> Hi Antti
>
> You can't have dvb_usb_device_properties as constant structure pointer.
>
> At run time it needs to be copied to a private area.
Having constant structure for properties was one of main idea of whole
change. Earlier it causes some problems when driver changes those values
- for example remote configuration based info from the eeprom.
> Two or more devices of the same type on the system will be pointing to
> the same structure.
Yes and no. You can define struct dvb_usb_device_properties for each USB ID.
> Any changes they make to the structure will be common to all.
For those devices having same USB ID only.
Changing dvb_usb_device_properties is *not* allowed. It is constant and
should be. That was how I designed it. Due to that I introduced those
new callbacks to resolve needed values dynamically.
If there is still something that is needed to resolve at runtime I am
happy to add new callback. For example PID filter configuration is
static currently as per adapter and if it is needed to to reconfigure at
runtime new callback is needed.
Could you say what is your problem I can likely say how to resolve it.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-06-15 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:11 dvb_usb_v2: use pointers to properties[REGRESSION] Malcolm Priestley
2012-06-15 22:54 ` Antti Palosaari [this message]
2012-06-16 0:35 ` Malcolm Priestley
2012-06-16 0:55 ` Antti Palosaari
2012-06-16 1:16 ` Antti Palosaari
2012-06-16 12:06 ` Malcolm Priestley
2012-06-16 15:52 ` Antti Palosaari
2012-06-16 18:12 ` Malcolm Priestley
2012-06-16 18:41 ` Antti Palosaari
2012-06-16 20:17 ` Malcolm Priestley
2012-06-16 20:27 ` Antti Palosaari
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=4FDBBD36.9020302@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).