<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
hi all,<br><br>sorry for spamming all the lists with this, but since nobody answered on my first try i have to repost this.<br>if nobody wants to take this one, please point me to the right documentation or the right people to ask directly.<br><br>i am currently working on the implementation of the low-level driver for the beagleboard/omap35xx i2c drivers.<br><br>i see that in the libi2c there are 5 hooks defined:<br><br>const rtems_libi2c_bus_ops_t beagle_i2c_ops = {<br> .init = beagle_i2c_init,<br> .send_start = beagle_i2c_send_start,<br> .send_stop = beagle_i2c_send_stop,<br> .send_addr = beagle_i2c_send_addr,<br> .read_bytes = beagle_i2c_read,<br> .write_bytes = beagle_i2c_write,<br> .ioctl = beagle_i2c_ioctl<br>};<br><br>my question is:<br><br>are the send_start, send_addr and send_stop functions supposed to actually _send_ the according signals to the bus when called?<br>or are they just preparing the device and the actual sending takes place in the read/write functions?<br><br>i have some difficulties generating the former behaviour on the beagleboard hardware.<br><br>thx for the great help so far, i am recently making really good progress, the interrupt handling is working now and i only have to <br>implement the i2c drivers and the clockdriver which i hope to do till xmas, so that u get a new BSP for RTEMS as a little xmas<br>present finally...<br><br>greetz,<br><br>claas </div></body>
</html>