| --- Log opened Fri Oct 16 00:00:28 2015 | ||
| -!- Netsplit over, joins: olofk, blueCmd_, robtaylor, julzmb, jpo, clopez, kaalia, stekern, heroux, GeneralStupid (+1 more) | 00:08 | |
| -!- Netsplit over, joins: Sockbr, rokka, _franck_, andrzejr | 00:08 | |
| mor1kx | [mor1kx] olofk opened pull request #32: Silence some synthesis warnings (master...master) https://github.com/openrisc/mor1kx/pull/32 | 13:18 |
|---|---|---|
| olofk | Three more and I'll get my t-shirt | 13:41 |
| mor1kx | [mor1kx] skristiansson closed pull request #32: Silence some synthesis warnings (master...master) https://github.com/openrisc/mor1kx/pull/32 | 17:59 |
| stekern | I want a t-shirt too | 18:02 |
| jeffesquivels | stekern: t-shirt? | 18:10 |
| wallento | for swiping bugs and warnings in mor1kx | 18:12 |
| stekern | what should it say? "I'm with moron-ekx"? | 18:15 |
| jeffesquivels | I thought you guys were referring to Digital Ocean's hacktoberfest t-shirt... my mistake :) | 18:16 |
| wallento | haha, nice one stekern | 18:21 |
| olofk | stekern: :) | 19:04 |
| olofk | And yes. The hacktoberfest thing was the reason why I decided to dust off these old patches that have been lying around.. so I'd say it works | 19:05 |
| olofk | Anyone who knows how bluetooth works in Linux? I compiled and loaded a bluetooth kernel driver now, but I was hoping that a bluetooth icon would pop up too | 19:10 |
| GeneralStupid | olofk: its long time ago i tried that... But AFAIK you need some tool like bluez-tools (debian) | 19:18 |
| andrzejr | olofk, does your patch fix something in the cache or is it just about warnings? | 19:47 |
| stekern | andrzejr: one thing you should consider if things break when you enable caches, bursting is only performed when caches are enabled | 19:53 |
| stekern | do your memory wrapper handle bursts correctly? | 19:54 |
| stekern | one other thing you could try, set all .ENABLE_BYPASS(0) that you can find in mor1kx to .ENABLE_BYPASS(1) | 19:56 |
| andrzejr | stekern, probably. It passes the olofk's test. | 19:56 |
| andrzejr | what does it do? | 19:56 |
| stekern | enables bypass logic in the ram instantiations | 19:56 |
| stekern | they *shouldn't* be needed anywhere, but just in case there's a snafu somewhere | 19:57 |
| andrzejr | I see. Is there any reason we are disabling these bypass paths? They look pretty harmless | 19:59 |
| stekern | they are, but they introduce (unnecessary) logic | 20:00 |
| andrzejr | I will try that. Are you suspecting timing violations in RAM or something else? | 20:07 |
| stekern | no, it has nothing to do with timing violations | 20:14 |
| stekern | if you need to read a just written value on the following clock cycle, you need the bypass | 20:15 |
| stekern | but in the places where the bypass is disabled, such a condition should not occur | 20:15 |
| andrzejr | I see, the RAM needs 2 cycles. | 20:20 |
| andrzejr | no difference, there must be some other issue | 21:17 |
| andrzejr | can linux or barebox at any circumstances issue an unaligned memory access? My ddr wrapper assumes that there are no transactions crossing boundaries of 128B. | 21:27 |
| --- Log closed Sat Oct 17 00:00:29 2015 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!