Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()

On Thu, 04 Jan 2007 20:59:08 -0200
Mauro Carvalho Chehab <[email protected]> wrote:

> > The largest value we use here is 0x02000000.  Perhaps v4l2_std_id shouldn't
> > be 64-bit?
> Too late to change it to 32 bits. It is at V4L2 userspace API since
> kernel 2.6.0.

You could perhaps make it 32-bit internally, and still 64-bit on the
kernel<->userspace boundary.   64-bit quantities are expensive..

> We can, however use this approach as a workaround, with
> the proper documentation. I'll handle it after I return from vacations
> next week.

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
    • From: Mauro Carvalho Chehab <[email protected]>

• References:
  • [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
    • From: Stelian Pop <[email protected]>
  • Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
    • From: Mauro Carvalho Chehab <[email protected]>

• Prev by Date: Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
• Next by Date: Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
• Previous by thread: Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
• Next by thread: Re: [PATCH] Fix __ucmpdi2 in v4l2_norm_to_name()
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]