Attention is currently required from: laforge.
tnt has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-e1d/+/29950 )
Change subject: support for e1-tracer hardware
......................................................................
Patch Set 1: Code-Review+1
(2 comments)
Patchset:
PS1:
Minor recommended change, but I'm not opposed to merging as-is.
File src/usb.c:
https://gerrit.osmocom.org/c/osmo-e1d/+/29950/comment/c0b18293_ed3b9adb
PS1, Line 993: if (!is_tracer) {
I would just test on if (line_data->ep_out) and if (line_data->ep_fb) rather than is_tracer.
A bit of a nit pick but it's more consistent with the ep_int test and also in the future if e1d is tracing, it's one less things to change.
--
To view, visit https://gerrit.osmocom.org/c/osmo-e1d/+/29950
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-e1d
Gerrit-Branch: master
Gerrit-Change-Id: I855e18c0f229bd473123f96303e60ab2de90677f
Gerrit-Change-Number: 29950
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: tnt <tnt(a)246tNt.com>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Tue, 01 Nov 2022 16:34:03 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-pcu/+/29933
to look at the new patch set (#3).
Change subject: tbf_ul: Assign DL-TBF if needed after UL-TBF has gone over contenion resolution
......................................................................
tbf_ul: Assign DL-TBF if needed after UL-TBF has gone over contenion resolution
If data received from SGSN is waiting to be sent to the MS, we may have
created a DL-TBF assignment over PCH if the MS was not in packet-active
mode. If the MS instead reaches back to the PCU asking for an UL-TBF, the
PCU has to wait until Content Resolution of the UL-TBF has succeeded in order
to attempt now to assign the DL-TBF over PACCH.
The delay was already there, but the trigger to attempt the DL-TBF
assignment upon UL-TBF contention reslution success was missing.
Related: OS#5700
Change-Id: Ib8f7ad2390485ce9fd76a9de6cd349a5f4037568
---
M src/tbf_ul.cpp
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-pcu refs/changes/33/29933/3
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/29933
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: Ib8f7ad2390485ce9fd76a9de6cd349a5f4037568
Gerrit-Change-Number: 29933
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: laforge, tnt.
Hello Jenkins Builder, tnt,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948
to look at the new patch set (#2).
Change subject: fw/e1-tracer: Additional USB configuration for "osmo-e1d compatible mode"
......................................................................
fw/e1-tracer: Additional USB configuration for "osmo-e1d compatible mode"
This adds a second USB configuration to the e1-tracer firmware. This
configuration is closer to the USB configuration of an icE1usb and hence
paves the way for using osmo-e1d with the tracer.
The main conceptual difference between the existing "legacy"
configuration and this new "e1d compatible" configuration is to have two
USB interfaces, one for each direction of the traced E1 interface. Each
interface has its own separate two altsettings, one for the disabled
and one for the enabled state.
Unmodified osmo-e1d will not work straight away with this, as it expects
ISO OUT and ISU Feedback endpoints, which a pure rx-only tracing device
of course doesn't have.
Related: OS#5733
Change-Id: I97062b9f12317b1b9b3855409c2380108cb921ff
---
M firmware/ice40-riscv/e1-tracer/usb_desc_app.c
M firmware/ice40-riscv/e1-tracer/usb_e1.c
M firmware/ice40-riscv/e1-tracer/usb_str_app.txt
3 files changed, 264 insertions(+), 67 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-e1-hardware refs/changes/48/29948/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-e1-hardware
Gerrit-Branch: master
Gerrit-Change-Id: I97062b9f12317b1b9b3855409c2380108cb921ff
Gerrit-Change-Number: 29948
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: tnt <tnt(a)246tNt.com>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: tnt <tnt(a)246tNt.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: laforge, tnt.
Hello Jenkins Builder, tnt,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29949
to look at the new patch set (#2).
Change subject: fw/e1-tracer: Initialize IDT82V2081 from within firmware in e1d mode
......................................................................
fw/e1-tracer: Initialize IDT82V2081 from within firmware in e1d mode
Initially it was a good choice to keep the LIU driver in the host
software (easier debugging/changes). However, we never really needed it
to do anything but initialization of the LIU.
So in order to avoid having to teach osmo-e1d or other software the
details about the LIU initialization, let's do this from the firmware
*if* the e1d compatible USB configuration is used.
Closes: OS#5733
Change-Id: Id2217ff4573c4eebd816318128f256e85fb3c3bd
---
M firmware/ice40-riscv/e1-tracer/Makefile
A firmware/ice40-riscv/e1-tracer/idt82v2081.c
A firmware/ice40-riscv/e1-tracer/idt82v2081.h
A firmware/ice40-riscv/e1-tracer/idt82v2081_no2spi.c
A firmware/ice40-riscv/e1-tracer/idt82v2081_regs.h
M firmware/ice40-riscv/e1-tracer/usb_e1.c
6 files changed, 314 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-e1-hardware refs/changes/49/29949/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29949
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-e1-hardware
Gerrit-Branch: master
Gerrit-Change-Id: Id2217ff4573c4eebd816318128f256e85fb3c3bd
Gerrit-Change-Number: 29949
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: tnt <tnt(a)246tNt.com>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: tnt <tnt(a)246tNt.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: tnt.
Jenkins Builder has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948 )
Change subject: fw/e1-tracer: Additional USB configuration for "osmo-e1d compatible mode"
......................................................................
Patch Set 1:
(2 comments)
File firmware/ice40-riscv/e1-tracer/usb_e1.c:
Robot Comment from checkpatch (run ID jenkins-gerrit-lint-646):
https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948/comment/8a7156e2_f283…
PS1, Line 200: else if (sel->bAlternateSetting == 1)
else should follow close brace '}'
Robot Comment from checkpatch (run ID jenkins-gerrit-lint-646):
https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948/comment/2a5ef29c_09bb…
PS1, Line 205: else
else should follow close brace '}'
--
To view, visit https://gerrit.osmocom.org/c/osmo-e1-hardware/+/29948
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-e1-hardware
Gerrit-Branch: master
Gerrit-Change-Id: I97062b9f12317b1b9b3855409c2380108cb921ff
Gerrit-Change-Number: 29948
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: tnt <tnt(a)246tNt.com>
Gerrit-CC: Jenkins Builder
Gerrit-Attention: tnt <tnt(a)246tNt.com>
Gerrit-Comment-Date: Tue, 01 Nov 2022 15:45:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment