| commit | b92f30d65aeb0502e2ed8beb80c8465578b40002 | |
| author | Christian Lamparter <chunkeey@web.de> | |
| Wed, 15 Oct 2008 02:07:16 +0000 (15 04:07 +0200) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Fri, 31 Oct 2008 23:00:33 +0000 (31 19:00 -0400) | ||
| tree | 7d2669d864df5368377dcad11c1bbf4be266eff5 | treesnapshot (tar.gz zip) |
| parent | 9de5776ff33a006b864341a6ec8d31f1a3c628cf | commitdiff |
p54: fix memory management
We have to be careful if multiple "control frames" are passed in a very short intervals to
the device's firmware. As p54_assign_address always put them into same memory location.
To guarantee that this won't happen anymore, we have to treat control frames like normal
data frames in the devices own memory management.
Signed-off-by: Christian Lamparter <chunkeey@web.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
We have to be careful if multiple "control frames" are passed in a very short intervals to
the device's firmware. As p54_assign_address always put them into same memory location.
To guarantee that this won't happen anymore, we have to treat control frames like normal
data frames in the devices own memory management.
Signed-off-by: Christian Lamparter <chunkeey@web.de>
Signed-off-by: John W. Linville <linville@tuxdriver.com>