From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-dvb@linuxtv.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, helge.hafting@aitel.hist.no,
mchehab@infradead.org
Subject: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and pseudo-authorities
Date: Mon, 30 Apr 2007 20:29:45 +0200 [thread overview]
Message-ID: <20070430182945.240530@gmx.net> (raw)
In-Reply-To: <20070430111414.0eefd4b0.akpm@linux-foundation.org>
-------- Original-Nachricht --------
Datum: Mon, 30 Apr 2007 11:14:14 -0700
Von: Andrew Morton <akpm@linux-foundation.org>
An: "Uwe Bugla" <uwe.bugla@gmx.de>
CC: Mauro Carvalho Chehab <mchehab@infradead.org>, helge.hafting@aitel.hist.no, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-dvb@linuxtv.org
Betreff: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and pseudo-authorities
> On Mon, 30 Apr 2007 19:25:47 +0200
> "Uwe Bugla" <uwe.bugla@gmx.de> wrote:
>
> > I did not manage to at least find one single unresolved module during
> compilation, and I have been working with this almost fantastic solution with
> several kernels for months now!
>
> That isn't what Mauro is saying. What he is saying is that the missing
> symbols will not be reported at build time. The kernel will all link
> correctly and will appear to load modules correctly.
>
> See, there's a third mechanism for symbol resolution which is used at
> runtime, not at build time: symbol_request().
>
> What Mauro is saying is that these changes will cause symbol_request() to
> return different results on some people's setups with different hardware,
> causing those setups to fail.
Hi Andrew,
But, even if this is the case, it should be transparent WHAT DIFFERENT HARDWARE
IS MEANT EXACTLY! DST AND DST_CA CANNOT BE MEANT - this I have made quite shure!
I swear I did not notice any errors - so as long as I cannot see through where the problem is, and as long as I have been working with my patches without the slightest noise for months now - where should I apply some additions then?
See, there's a third mechanism for symbol resolution which is used at
runtime, not at build time: symbol_request().
If this symbol_request() appears at runtime, then there should be some feedback in dmesg or any other kind of syslog.
But I swear I haven't seen any kind of bad or counterproductive messages like this!
My system runs excelent with my patches - so why should I care?
I meanwhile have sent my patches to someone, he will have a look at them - and we all will see what happens then.
Above that I will at least try to enhance those two patches by a dvb-pll.c deselection feature which I said very politely to Trent that I am missing it.
And I want to get out now of that horrible discussion - I am exhausted.
Cheers
Uwe
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
next prev parent reply other threads:[~2007-04-30 18:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 18:22 Critical points about kernel 2.6.21 and pseudo-authorities Uwe Bugla
2007-04-29 18:49 ` Linus Torvalds
2007-04-29 20:59 ` Uwe Bugla
2007-04-29 21:19 ` Linus Torvalds
2007-04-29 23:00 ` Uwe Bugla
2007-04-30 0:58 ` [linux-dvb] " hermann pitton
2007-04-30 11:02 ` Uwe Bugla
2007-04-30 11:21 ` Helge Hafting
2007-04-30 11:50 ` Uwe Bugla
2007-04-30 15:04 ` Helge Hafting
2007-04-30 15:24 ` Markus Rechberger
2007-04-30 16:09 ` Uwe Bugla
2007-04-30 16:56 ` Mauro Carvalho Chehab
2007-04-30 17:25 ` Uwe Bugla
2007-04-30 18:04 ` Linus Torvalds
2007-04-30 18:07 ` Uwe Bugla
2007-04-30 18:14 ` Andrew Morton
2007-04-30 18:29 ` Uwe Bugla [this message]
2007-04-30 18:29 ` Jan Engelhardt
2007-04-30 19:42 ` Markus Rechberger
2007-04-30 11:35 ` Thomas Gleixner
2007-04-30 11:48 ` Markus Rechberger
2007-04-30 12:37 ` Uwe Bugla
2007-04-30 13:06 ` Markus Rechberger
2007-04-30 14:09 ` Uwe Bugla
2007-04-30 15:30 ` Michael Krufky
2007-04-30 16:39 ` Uwe Bugla
2007-04-30 14:49 ` Linus Torvalds
2007-04-30 15:19 ` Uwe Bugla
2007-04-30 15:56 ` Linus Torvalds
2007-04-30 22:41 ` Trent Piepho
2007-04-30 22:58 ` Manu Abraham
2007-04-30 23:08 ` Markus Rechberger
2007-04-30 23:40 ` Uwe Bugla
2007-05-01 0:19 ` Manu Abraham
2007-05-01 0:29 ` Markus Rechberger
2007-05-01 9:23 ` Uwe Bugla
2007-04-30 23:05 ` Uwe Bugla
2007-04-30 23:20 ` hermann pitton
2007-04-30 1:37 ` Trent Piepho
2007-04-30 10:47 ` Uwe Bugla
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=20070430182945.240530@gmx.net \
--to=uwe.bugla@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=torvalds@linux-foundation.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