On Wed, Oct 18, 2006 at 07:54:41AM +0100, Keith Whitwell wrote:
> This is all a little confusing as the driver doesn't really use that
> path in normal operation except for a single command - MI_FLUSH, which
> is shared between the architectures. In normal operation the hardware
> does the validation for us for the bulk of the command stream. If there
> were missing functionality in that ioctl, it would be failing
> everywhere, not just in this one case.
>
> I guess the questions I'd have are
> - did the driver work before the kernel upgrade?
> - what path in userspace is seeing you end up in this ioctl?
> - and like Keith, what commands are you seeing?
>
> The final question is interesting not because we want to extend the
> ioctl to cover those, but because it will give a clue how you ended up
> there in the first place.
Here's a list of all the failing commands I've seen so far:
3a440003
d70003
2d010003
e5b90003
2e730003
8d8c0003
c10003
d90003
be0003
1e3f0003
-ryan
-
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/
[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]
