From: Steven Toth <stoth@linuxtv.org>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Steven Toth <stoth@hauppauge.com>,
Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: cx18-0: ioremap failed, perhaps increasing __VMALLOC_RESERVE in page.h
Date: Fri, 02 May 2008 11:00:38 -0400 [thread overview]
Message-ID: <481B2C96.2050109@linuxtv.org> (raw)
In-Reply-To: <481B1027.1040002@linuxtv.org>
Michael Krufky wrote:
> I had this issue before dtv support was properly added to the cx18 driver.
The DTV disabling is a red herring.
>
> With digital working fine, the issue had disappeared.
>
> Now, using cx18 in the master branch, whose dtv side is crippled due to
> lack of the mxl driver, the error is back.
Try the hg/~stoth/merge tree, with the feature re-enabled and the newer
mxl5005 driver. Does this help?
>
> The cx18 driver can be loaded on my system once. If I unload it, then I
> get this every time I try to modprobe it again.
I can't repro the issue, but the unwind code (at least at first glance)
looked OK to me.
Hans or Andy should comment on this, it's really their code.
...
Regards,
Steve
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-05-02 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 12:59 cx18-0: ioremap failed, perhaps increasing __VMALLOC_RESERVE in page.h Michael Krufky
2008-05-02 13:47 ` Andy Walls
2008-05-02 15:22 ` Steven Toth
2008-05-12 14:42 ` Steven Toth
2008-05-12 14:48 ` mkrufky
2008-05-15 2:24 ` Andy Walls
2008-05-15 12:57 ` Michael Krufky
2008-05-15 23:53 ` Andy Walls
2008-05-12 14:48 ` Hans Verkuil
2008-05-12 23:20 ` Andy Walls
2008-05-02 15:00 ` Steven Toth [this message]
2008-05-03 2:43 ` [PATCH] Fix potential cx18_cards[] entry leaks Andy Walls
2008-05-03 13:33 ` [PATCH] 2nd try: " Andy Walls
2008-05-12 15:05 ` [PATCH] " Hans Verkuil
2008-05-12 23:30 ` Andy Walls
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=481B2C96.2050109@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=mkrufky@linuxtv.org \
--cc=stoth@hauppauge.com \
--cc=video4linux-list@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.