구차니의 잡동사니 모음

$ apt-cache search git | grep ^git

git - fast, scalable, distributed revision control system

git-core - fast, scalable, distributed revision control system (obsolete) 

git-all - fast, scalable, distributed revision control system (all subpackages)

$ sudo apt-get install git 

$ git config --global user.name "이름"

$ git config --global user.email "이메일주소"

$ git config --global color.ui "auto" 

$ git config --list

user.name=이름

user.email=이메일주소

color.ui=auto

$ vi ~/.gitconfig

[user]

        name = 이름

        email = 이메일주소

[color]

        ui = auto 

$ mkdir git_repo

$ cd git_repo

$ git init --bare --shared

초기화: 빈 공유 깃 저장소, 위치 /home/odroid/src/tt/

$ ll

합계 40

drwxrwsr-x 7 odroid odroid 4096  4월 24 16:08 ./

drwxrwxr-x 5 odroid odroid 4096  4월 24 16:08 ../

-rw-rw-r-- 1 odroid odroid   23  4월 24 16:08 HEAD

drwxrwsr-x 2 odroid odroid 4096  4월 24 16:08 branches/

-rw-rw-r-- 1 odroid odroid  126  4월 24 16:08 config

-rw-rw-r-- 1 odroid odroid   73  4월 24 16:08 description

drwxrwsr-x 2 odroid odroid 4096  4월 24 16:08 hooks/

drwxrwsr-x 2 odroid odroid 4096  4월 24 16:08 info/

drwxrwsr-x 4 odroid odroid 4096  4월 24 16:08 objects/

drwxrwsr-x 4 odroid odroid 4096  4월 24 16:08 refs/

$ du -h

8.0K    ./info

44K     ./hooks

4.0K    ./objects/info

4.0K    ./objects/pack

12K     ./objects

4.0K    ./branches

4.0K    ./refs/heads

4.0K    ./refs/tags

12K     ./refs

96K     .

Control and LEDs

• RS - this is the reset pin. To reset the module, pull this pin to ground. It does not affect pairing.
• L2 - this is the same output that is connected to the PairLED. If you want to put this in a box and have an external Pair indicator LED, wire an LED from this pin, through a 1K resistor, to ground.
• PB - this is the pair button pin. It is connected to the button onboard that is used to reset the pairing. If you want to make another, external pair button, connect a switch from this key to 3V (not ground!)
  
• L1 - this is the same output that is connected to the KeyLED. If you want to put this in a box and have an external Key-press indicator LED, wire an LED from this pin, through a 1K resistor, to ground.
• RX - this is the UART input, used if you want to send UART->Keypress data, or re-map the buttons. It is 5V compliant, use 3V-5V TTL logic, 9600 baud.
• TX - this is the UART output, used for watching debug data or re-mapping the buttons. It is 3V logic level output.

    $$$                    //Enter command mode (no CR/LF)

    CMD

    SM,6                   //Set Mode = pairing

    AOK

    SN,SNESpad             //Set Name

    AOK

    S~,6                   //Set profile = HID

    AOK

    SH,0240                //Set report descriptor = joypad

    AOK

    R,1                    //Reset for settings to take effect.

SoftwareSerial bluetooth(bluetoothRX, bluetoothTX);

//...

// Command Mode

// --------------

bluetooth.begin(9600);

delay(50); 

bluetooth.print("$$$");

delay(50); 

bluetooth.print("SN,HIDJoystick\r\n");

delay(50); 

bluetooth.print(" SU,57\r\n");

delay(50); 

bluetooth.print("S~,6\r\n");

delay(600); 

bluetooth.print("SH,0240\r\n");

delay(200); 

bluetooth.print("R,1\r\n");  

delay(400);

// HID Joystick Report

// --------------

bluetooth.write((byte)0xFD); //Start HID Report

bluetooth.write((byte)0x6);  //Length byte

// 1. X/Y-Axis

bluetooth.write(45);  //First X coordinate

bluetooth.write(-33); //First Y coordinate

// 2. X/Y-Axis

bluetooth.write(45);  //Second X coordinate

bluetooth.write(-33); //Second Y coordinate

// Buttons

bluetooth.write(B10000001); // Second Byte (Buttons 1-8)

bluetooth.write(B10000000); // Second Byte (Buttons 9-16)

Please notice that sudo is necessary to run this script. This script will automatically do 

these tasks in order:

1. Enable I2C on your Raspberry Pi

2. Install i2cctools, if it is not installed yet

3. Configure Bluetooth to use minicUART (Raspberry Pi 3 only)

4. Install wiringPi, if it is not installed yet

5. Install Witty Pi programs, if they are not installed yet

2.7.15 Power Control Signals

i.MX6 Qseven PMIC SOM supports two power control signals PWGIN and PWRBTN# on Qseven Edge connector.

PWGIN input from Qseven Edge connector is the active high signal which is used to enable the power of i.MX6

Qseven PMIC SOM. For more details on PWRGIN signal usage, refer section 3.1.2.

i.MX6 Qseven PMIC SOM supports PWRBTN# input from Qseven Edge connector which is the active low signal and

connected to i.MX6 CPU’s ONOFF pin. This pin can be used to On/Off the i.MX6 CPU by connecting push button in

the carrier board. When the board power is On, a button press between 750ms to 5s will send an interrupt to core to

request software to bring down the i.MX6 safely (if software supports). Otherwise, button press greater than 5s

results in a direct hardware power down which is applicable when software is unable to power Off the device. When

the i.MX6 CPU power supply is Off, a button press greater in duration than 750ms asserts an output signal to request

power from a power IC to power up the i.MX6 CPU. 

 +static irqreturn_t pb_isr(int irq, void *dev_id)

+{

+ int ret;

+ int state;

+

+ ret = intel_soc_pmic_readb(DC_TI_SIRQ_REG);

+ if (ret < 0) {

+ pr_err("[%s] power button SIRQ REG read fail %d\n",

+ pb_input->name, ret);

+ return IRQ_NONE;

+ }

+

+ state = ret & SIRQ_PWRBTN_REL;

+

+ if (force_trigger && state) {

+ /* If we lost the press interrupt when short pressing

+ * power button to wake up board from S3, simulate one.

+ */

+ input_event(pb_input, EV_KEY, KEY_POWER, 1);

+ input_sync(pb_input);

+ input_event(pb_input, EV_KEY, KEY_POWER, 0);

+ input_sync(pb_input);

+ } else {

+ input_event(pb_input, EV_KEY, KEY_POWER, !state);

+ input_sync(pb_input);

+ pr_info("[%s] power button %s\n", pb_input->name,

+ state ? "released" : "pressed");

+ }

+

+ if (force_trigger)

+ force_trigger = 0;

+

+ return IRQ_HANDLED;

+}

+

+static int pb_probe(struct platform_device *pdev)

+{

+ int ret;

+

+ pwrbtn_irq = platform_get_irq(pdev, 0);

+ if (pwrbtn_irq < 0) {

+ dev_err(&pdev->dev,

+ "get irq fail: irq1:%d\n", pwrbtn_irq);

+ return -EINVAL;

+ }

+ pb_input = input_allocate_device();

+ if (!pb_input) {

+ dev_err(&pdev->dev, "failed to allocate input device\n");

+ return -ENOMEM;

+ }

+ pb_input->name = pdev->name;

+ pb_input->phys = "power-button/input0";

+ pb_input->id.bustype = BUS_HOST;

+ pb_input->dev.parent = &pdev->dev;

+ input_set_capability(pb_input, EV_KEY, KEY_POWER);

+ ret = input_register_device(pb_input);

+ if (ret) {

+ dev_err(&pdev->dev,

+ "failed to register input device:%d\n", ret);

+ input_free_device(pb_input);

+ return ret;

+ }

+

+ ret = request_threaded_irq(pwrbtn_irq, NULL, pb_isr,

+ IRQF_NO_SUSPEND, DRIVER_NAME, pdev);

+ if (ret) {

+ dev_err(&pdev->dev,

+ "[request irq fail0]irq:%d err:%d\n", pwrbtn_irq, ret);

+ input_unregister_device(pb_input);

+ return ret;

+ }

+

+ return 0;

+}

> +int intel_soc_pmic_set_pdata(const char *name, void *data, int len)

> +{

> + struct cell_dev_pdata *pdata;

> +

> + pdata = kzalloc(sizeof(*pdata), GFP_KERNEL);

> + if (!pdata) {

> + pr_err("intel_pmic: can't set pdata!\n");

> + return -ENOMEM;

> + }

> +

> + pdata->name = name;

> + pdata->data = data;

> + pdata->len = len;

> +

> + list_add_tail(&pdata->list, &pdata_list);

> +

> + return 0;

> +}

> +EXPORT_SYMBOL(intel_soc_pmic_set_pdata); 

GAL : Generic Logic Array

PAL :  Programmable Array Logic

PLD : Programmable Logic Device

CPLD : Complex Programmable Logic Device

FPGA : Field Programmable Gate Array