a notification about downstream latency change, when it really
should have send that to the connected inputs. This is now done
by the PublishEventLatencyChange() function.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4567 a95241bf-73f2-0310-859d-f6bbb57e9c96
code, since I made the problem causing changes on another machine...
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4470 a95241bf-73f2-0310-859d-f6bbb57e9c96
atomic_test_and_set() to the OpenBeOS headers (prefixed BFS versions with '_').
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4446 a95241bf-73f2-0310-859d-f6bbb57e9c96
to get_next_partition().
If a wannabe partition fails its checksum test, all partitions that might come
later are now skipped. Added a ToDo item for what would be a nicer dealing with
such errors.
get_next_partition() and search_rdb() are now static.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4444 a95241bf-73f2-0310-859d-f6bbb57e9c96
is now tested for partition_blocks as well.
Makes use of the new endian-aware structure methods.
If a partition is out of bounds (starts or reaches beyond the available
disk space), it won't be registered anymore - not sure if that's sooo
desirable, though.
Removed some unneeded debug output.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4443 a95241bf-73f2-0310-859d-f6bbb57e9c96
the file path to be part of the module name (that's not the case for BeOS, is it?).
Also added some more debug output, and now only allocate a new rigid_disk_block
if we are going to need it.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4441 a95241bf-73f2-0310-859d-f6bbb57e9c96
this "shell" (the new DiskDeviceManager module API).
Hope for the best :-)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4440 a95241bf-73f2-0310-859d-f6bbb57e9c96
aggravating the compiler when used in the DriveSetup add-on.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4412 a95241bf-73f2-0310-859d-f6bbb57e9c96
of, say, src/add-ons/drive_setup/fs/udf/, because we won't need it for OBOS::R1,
but will instead need a disk device manager add-on, which will be written later.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4405 a95241bf-73f2-0310-859d-f6bbb57e9c96
I have made an (ugly) hack around the transmit problem (but then again, aren't
hacks ugly all the time?). I still don't know if this is the proper thing, but
the point is that it seems to work now. I don't know if it is my mistake or
the cards mistake that I cannot schedule more than one write at a time, but
I'm looking into this. I don't know the difference in performance between this
driver and the one in R5, but I'm guessing this one's still a bit slower. I'll
continue to hack the driver in order to maximize performance.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4364 a95241bf-73f2-0310-859d-f6bbb57e9c96
init_driver() - also added a matching uninit_driver() (just in case :)).
Replaced in8()/out8() with calls to the ISA bus manager (NewOS change 1804).
Removed unused includes.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@4301 a95241bf-73f2-0310-859d-f6bbb57e9c96
