But file_read on file pointer doesn't work in the same way as read on file
descriptor, even if it is in the same thread - right after file_open!
That would be surprising because read() just calls file_read(). I would
expect the behaviors to be the same.
If there is a semaphore locking
Hi!
Is it really matters? I think the issue is more about file descriptors,
file pointers and so on.
CAN is configured with extended ID. Yes, I did use CAN app from examples,
it works.
Implementation in my own app also works fine if I use file descriptor when
opened /dev/can0. In different
Oleg: do you use an extended ID or standard ID? And do you use the CAN app from
examples?
Verstuurd vanaf mijn iPhone
> Op 15 jan. 2020 om 22:02 heeft Oleg Evseev het volgende
> geschreven:
>
> Hi!
>
> When I use usual file descriptor for can device:
> file_open(>file, "/dev/can0",
Hi!
When I use usual file descriptor for can device:
file_open(>file, "/dev/can0", O_RDWR);
everything works, thread blocks if further read() and, when can message
receive, returns correct nbytes.
When I open can0 with
file_open(, "/dev/can0", O_RDWR);
it opens correctly and file_ioctl seems to
