Skip to content

Add license#1

Open
platonbjs wants to merge 1 commit intoMotorolaMobilityLLC:masterfrom
platonbjs:feature
Open

Add license#1
platonbjs wants to merge 1 commit intoMotorolaMobilityLLC:masterfrom
platonbjs:feature

Conversation

@platonbjs
Copy link

Hola!
Somos un grupo de estudiantes de la Universidad Complutense de Madrid (UCM) y estamos
haciendo una campaña de concienciación sobre el uso de licencias.

Razones por las que usar una licencia:

  • Es FáCIL de usar: escoge la licencia, copia el texto genérico y listo! Ya puedes usarla en tus proyectos. En el siguiente link puedes encontrar más información:
  • LIMíTAS que usos pueden tener las personas para usar tu contenido, de esta manera evitas problemas de copias y plagios
  • Compartir es poder! Las licencias libres te dan credito en todo momento permitiendo que otros usen tu trabajo bajo TUS condiciones.
    En el siguiente video se explican los tipos de licencias para que puedas escoger una que se adapte a tus necesidades

Hemos elegido la licencia MIT para este pull request. En este link puedes encontrar mas informacion sobre esta licencia

Gracias por tu atención! Esperamos que te haya servido de ayuda


Hello!
We are a group of students of Universidad Complutense de Madrid (UCM) and we are working on an awareness campaign about types and uses of licences.

There are many reasons to use licences in your code:

  • It's EASY to use: choose the licence, copy the generic text and ready! Now you can use it in your projects You can found more information in the following link

  • You LIMIT the uses of your code, in this way you will avoid possible legal problems about copies and plagiarism

  • Share is power! The freeware licences give to you credit all the time. Allow third people use it with YOUR conditions

The following youtube link show the existing types of licences to choose one which adapt better to your needs

We have chosen MIT license for this pull request. In this link, you can get more information about this license

Thank you a lot for your attention! We hope you the contents has been helpful

mbissaromoto pushed a commit that referenced this pull request Apr 10, 2025
Hit following issue of link switch when LL-SAP existed.
1. Link switch was received on VDEV-1 (partner link).
   a. Link switch cmd was added to serial active queue, existing peer
      was deleted as part of link switch disconnect.
   b. Link switch connect started but got deferred due to LL-SAP Bearer
      switch transition, when WLAN_CM_SM_EV_BEARER_SWITCH_COMPLETE
      received, a new connect cmd was added to serial pending queue,
      link switch was blocked here.

2. Disconnect from userspace was received
   a. The disconnect on VDEV-1 here notified MLO-manager to terminate
      ongoing link switch.
   b. Link switch confirmation was sent to F/W as failure.
   c. link switch cmd was removed from serial active queue.

3. Connect cmd queued in #1.b was activated and moved VDEV-1 state to
connecting.
   a. New peer got created but PE session wasn't yet created.
   b. Disconnect from #2.a changed the VDEV-1 state from connecting to
      disconnecting.
   c. While processing the disconnect in #3.b, peer delete for the peer
   created in #3.a didn’t happen as disconnect didn’t proceed when pe
   session not found.

To fix it, for link switch, don't add new connect cmd to serial queue
after LL-SAP Bearer switch since link switch cmd is queued already.

1. Link switch is received on VDEV-1 (partner link).
   a. links witch cmd was added serial active queue, existing peer
      gets deleted as part of link switch disconnect.
   b. Link switch connect starts but gets deferred due to LL-SAP Bearer
      switch transition, WLAN_CM_SM_EV_CONNECT_ACTIVE is sent after
      WLAN_CM_SM_EV_BEARER_SWITCH_COMPLETE received, bss peer creat cmd
      is sent to F/W.

2. Disconnect from userspace is received when link switch unfinished.
   a. The disconnect on VDEV-1 here notified MLO-manager to terminate
      ongoing link switch.
   b. If BSS peer created, mlme_cm_bss_peer_delete_req will be called to
	delete it.
   c. Link switch confirmation is sent to F/W as failure.
   d. link switch cmd is removed from serial active queue.

Change-Id: I13ba820bd0240d062c7cd47ec0e53ae1a27d5b58
CRs-Fixed: 3752437
mbissaromoto pushed a commit that referenced this pull request Nov 6, 2025
Host driver sends the same bss for both assoc and partner
links, leading to undesired behavior in kernel.

Scenario:
1) Host driver fills the assoc bss in link id 0 to handle
roamed indication for the legacy connections.
2) The assoc link bss is filled in link idx 1.
3) The patner link bss is not found, therefore not filled
in link idx 0.
4) The assoc bss filed in #1 to handle legacy connection
gets retained. Therefore, host ends up sending same bss for
two links.

To fix this, reset the bss entry on the link index of the
partner link in the roamed indication if the bss is not
found.

Change-Id: I9e941e4a9ff9760ada4c8c42015c925cc08b528a
CRs-Fixed: 4106746
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant