On 08/28/2012 03:48 PM, Adam Barta wrote:
I think you can assume to read 1 (32 bit word) or (4bytes) as a
minimum from each of the register file descriptors safely?
No, on reading I get back zero bytes. I tried that with buffering=0 and
buffering=4.
Tom
On Wed, Aug 29, 2012 at 12:39 AM, Tom Kuiper <[email protected]
<mailto:[email protected]>> wrote:
On 08/28/2012 03:36 PM, Adam Barta wrote:
Looking in /proc most other "kernel generated files" for example
/proc/interrupts or /proc/mdstat also have 0 filesizes.
Well, that seems pretty common with things that aren't really
files but I don't know how to get Python to read more than teh
nominal file size if it is supposed to look like a file.
I'm going to see if I can restore the file size some way. It
would be a hack but if it works I'll move on.
Cheers
Tom
On Wed, Aug 29, 2012 at 12:28 AM, Tom Kuiper <[email protected]
<mailto:[email protected]>> wrote:
On 08/28/2012 03:11 PM, Tom Kuiper wrote:
I have the feeling that the file length going to zero on
a simple write is unintended and been lurking in the
borph code since no one ever tried such a simple OS-level
write. I'm guessing that the file pointer, which is
reset to zero before the write, is not advanced after the
write.
Well, scratch that idea. The file pointer is definitely 4
before I close the file.
Tom
--
*Adam Barta*
c: +27 72 105 8611 <tel:%2B27%2072%20105%208611>
e: [email protected] <mailto:[email protected]>
w: www.ska.ac.za <http://www.ska.ac.za>
--
I or me?http://www.oxforddictionaries.com/page/145
--
*Adam Barta*
c: +27 72 105 8611
e: [email protected] <mailto:[email protected]>
w: www.ska.ac.za <http://www.ska.ac.za>
--
I or me? http://www.oxforddictionaries.com/page/145
