dev: raw disks are 64-bit, so a real drive stops wrapping at 4 GB

struct file already carried a uint64 offset and bread already took a
uint64 block number. The narrowing was one boundary in the middle:
devsw's read and write took a 32-bit uint, so fileread passed a 64-bit
f->off into a 32-bit parameter and the top half was discarded.

The effect was not a refusal at 4 GB but silent wraparound past it. A
read at 5 GB returned the bytes at 1 GB, reporting success. disk.c had a
DISK_MAX_BYTES constant documenting the limit, and nothing anywhere
referenced it -- the cap was described but never enforced, which is the
worst of the three options.

The signature is now uint64 across all nine files that carry it, and
diskread/diskwrite no longer narrow the block number on the way to
bread. Widening this is a prerequisite for NVMe and for any real disk:
namespaces start well above 4 GB and the failure mode reads valid data
from the wrong place.

Verified end to end rather than by inspection. A 6 GB sparse image with
"PAST4GB-MARKER-OK" written at byte 5368709120, attached as /dev/hdb to a
ramdisk-root kernel so device 1 was free:

  # dd if=/dev/hdb bs=4096 skip=1310720 count=1 | od -c | head -2
  0000000   P   A   S   T   4   G   B   -   M   A   R   K   E   R   -   O

Under the old code that offset truncates to 1 GB, where the image is
zeroes. The whole path is exercised: f->off, devsw, diskread, bread and
ide.c's LBA48.

Worth recording for next time: `make ramroot` stages the ESP itself, and
running `make esp` afterwards rebuilds the kernel without RAMROOT and
silently undoes it. The tell is a 855 KB kernel where a 25 MB one is
expected.

110 [ok], no failures, on the default build.

kernel/dev/input.c

@@ -233,7 +233,7 @@ input_ioctl(struct inode *ip, int request, addr_t arg)
 // desynchronise the reader permanently -- every later event would be split
 // across two reads and reassembled wrong.
 int
-inputread(struct inode *ip, uint off, char *dst, int n)
+inputread(struct inode *ip, uint64 off, char *dst, int n)
 {
   struct input_dev *d;
   int got = 0;
@@ -266,7 +266,7 @@ inputread(struct inode *ip, uint off, char *dst, int n)
 // evdev accepts writes to set keyboard LEDs. There are no LEDs to set here,
 // and a program that writes one should not see an error for it.
 int
-inputwrite(struct inode *ip, uint off, char *src, int n)
+inputwrite(struct inode *ip, uint64 off, char *src, int n)
 {
   return n;
 }